I wish this old legend would die already. It's not even perf/grad season.

When a border or name is disputed, this is shown with the "given names" in the countries on each side of the dispute, and with both names (one in brackets) everywhere else.

I read so many similar stories and I'm still shocked.

It took 8 months from my first acute back pain problems to the diagnostic.

Ok, they have the trademark, but how does it give them the permission to reuse or copy the original game assets, designs, etc?

It doesn't. But you can only fight for the restriction of those who do if you have the resources. I doubt he has.

Anyone can illegally take anyone's content and use it. It's not until the courts are involved you can't.

Some are just better funded than others, like Disney.

It's interesting how so many people miss this. I often hear "Big Co. can't do Y, it'd be a violation of X!". Well of course they can. No one is going to pull C-Level executives from their beds in the middle of the night because they did something you don't like.

Likewise, lots of people seem to think that just because some IP has entered the public domain or it's "fair use" you won't get sued if you start using it. Of course you'll get sued. The plaintiff doesn't expect to win, they expect you to give up. I can already hear the sound of a thousand keyboards typing out responses to this how numerous jurisdictions have laws against "SLAPP" lawsuits.

Very little at the scale of this codebase is still a lot.

From where I sit (SRE), I see a lot of Python which is very much mission critical.

is it really Python though ?

yes, SRE uses loads of python, despite a decade+ pseudo-mandate to encourage Go

I have heard that SRE teams can get away with this on the idea that SREs usually are not as good at software engineering as SWEs, so some bad engineering practices can fly.

I never saw Python actually get used, though, in the projects I worked on.

That's not my experience.

First, there are two SRE ladders: SRE-SWE and SRE-SysEng. SRE-SWE have the same interviews and hiring bar as SWEs. SysEng have less coding interviews but I think the interview questions are more practical and less algorithm oriented.

Still, SREs are subject to the same rules and policies as SWEs when it comes to submitting code.

And in the end, I don't see why using python on some projects would be a bad engineering practice

This is blatantly false, along with the idea that there’s only very little python.

On the scale of the company, Python is a very small language, and the very important stuff is 100% not in Python. However, 100,000 people work at Google, and probably over a million have it on their resume, so "small" at Google is "big" for a lot of people.

Google can definitely afford (in technical terms) to be a follower rather than a leader when it comes to Python.

I believe it also depends on your location. I only see sponsored tiles when traveling in some countries.

The reason is quite simple: why spend engineering headcount on a less successful product?

> Some wouldn't have been viable, sure. Others were probably too ingrained in Google's hardware/software ecosystem to be separated out (although I wonder if nowadays everything Google runs on its cloud offering, which would make it simpler, just change the billing).

Google Cloud is built on top of Google's tech ecosystem, not the other way around.

Because things need time and alignment of incentives between creators and consumers and if you interfere in that relationship all the time things will never ever succeed. The last thing any project needs is an investor with a majority interest that fucks up your plans all the time, can take your employees away at will and can axe the project at any time because it doesn't perform according to their metrics.

That's why VCs take a minority stake in start-ups. The trouble usually begins when the founders dilute to the point that they no longer have a majority.

Google must diversify its source of revenue, that's the purpose of hardware, Cloud, Youtube premium and others. It is also why they sell access to APIs.

This is not bard.

Nolan not using CGI is like Tom Cruise doing Mission: Impossible stunts himself. These affirmations are ambiguous and misleading.

In the case of Oppenheimer (and other Nolan movies) they use a lot of practical effects but they are eventually digitally composited, color corrected and edited.

> The director was not attempting to claim that there was no CGI in Oppenheimer at all. He was instead stating that there are no shots in the movie that were entirely created using visual effects.

see https://screenrant.com/how-much-oppenheimer-real-cgi/

There’s a big difference between digital video editing and compositing vs creating completely artificial scenes with computer-generated 3D models and effects.

Yes, the later is what Nolan avoids.

But when he says "the movie is done without CGI shots", he can't ignore that most people will assume the movie is also made without digital editing and compositing.