phlegmy

No, a gaming pc 'can' use 750 watts. But it won't be using 750 watts 100% of the time.
Power supplies only draw what they need, not their full rated capacity.

GPU's also downclock and lower their power draw when they aren't being stressed to their limits.

Lunch breaks cut 30-60 minutes out of those 8 hours.

And that article estimated 5000 employees internationally, which includes management, marketing, programmers, visual artists, musicians, sound engineers, voice actors, qa, translators, external consultants/contractors, and many more.
These are all people who have helped make the game at some point, and does not mean these people were in-office or employed for the entire development process.

Very few of those roles require top-end machines, and even fewer require their systems to be running at full speed 100% of the time.

What? No. That would be crazy.

I write BDFPR from the bottom.
Though I'm also a heretic who starts G from the middle, so don't listen to me.

But its not 230 murders per 100,000. It's 289 murders total, for the entire population that year.
0.233 out of 100,000 were murdered.
That's 0.000233% of 100,000 people.

Same for people who've drunk tap water! Makes me wonder what they're really putting in our water...

Practically impossible for this developer? Maybe. Technically impossible? No.

We do have realtime GI solutions which don't require raytracing (voxel cone tracing, sdfgi, screenspace, etc). None of which require any 'special' hardware.

Raytracing is just simpler and doesn't need as much manual work to handle cases where traditional rasterisation might fail (eg; light leaking). But there's not many things it can do which we can't already achieve with rasterisation tricks.
Raytracing is mostly useful for developers who don't have the time/budget/skillset to get the same visual quality with traditional rasterisation.

However, in an industry which seems to prioritise getting things released as cheaply and quickly as possible, we're starting to see developers rely heavily on raytracing, and not allocating many resources into making their non-rt pipeline look nice.
Some are even starting to release games which require raytracing to work at all, because they completely cut the non-rt pipeline out of their budget.

So I'd argue that you're incorrect in theory, but very correct in practise (and getting even more correct with time).

I only use lemmy regularly.
I'll still check specific subreddits which don't have a lemmy equivalent, but not that often, and never signed in or with the official app.

Callbacks and decorators are fine, but callbacks/decorators to a function which itself takes a function pointer and returns another function pointer are crazy.

I've thankfully never had to use recursive callbacks or decorators, but it seems like it could very quickly become difficult to keep track of.

If you actually use code like this you're insane.

Do you say shit like that because nobody can tell the difference between your watch and a cheap one?

So, hormones don't exist?
Intersex people don't exist?
Trans people don't exist?
And what, we're all either 100% male or 100% female and there is never a grey area in biology?

Don't make the conscious decision to remain ignorant, you're keeping yourself back.

Looks like a piet program