I count 10 European companies on this list, and 20 US.

Maybe is not as bad as you think?

https://en.wikipedia.org/wiki/List_of_largest_companies_by_r...

It has been shown that you need around 14 days of interrupted rest to recover from stress etc.

The European laws are not some random thing we made up because we are lazy. It is to ensure workers are well rested and ready for a new working year. Hence in long term it will also benefit employers.

Some personal anecdata: I notice an immediate difference when I come back after a long vacation. The first 2-3 months I work at top efficiency, get probably done twice as much as I would do any other month.

The actually ridiculous part is not that.

It’s the fact that our browsers don’t solve this issue in a standardized way.

Everyone who serves HTTP in the Eu and includes third party tracking, shows you an idiosyncratic consent banner. Often these things download a large amount of JS as well.

That’s completely and utterly idiotic.

- It’s confusing for users.

- It interrupts the user’s flow everytime they visit a site.

- It’s bad for overall performance.

- It’s bad for people who publish content.

- Developers have to defer to legal experts for trivial stuff out of FUD.

- It doesn’t work correctly on the technical side.

- It doesn’t work from a user’s perspective, because they just get annoyed or uncertain and falsely consent!

Nobody wins.

It should just be a standard, global feature in browsers. A site should only ask you _once_, if at all from a user’s perspective.

The browser should send a “profiling and tracking” whitelist, or simply make it available via a JS API.

Why is this not the case?

Yes, but in practice, no. These games are usually coded as a loop that runs with full CPU as fast as it can (unless capped, which the old one wasn’t), using as much cpu as is available. In that case, the fps is a side effect of how long the loop takes to run each pass (which is what happened here) - i.e. you don’t determine the fps, the fps is a result of how complicated or (in)efficient your code is. So going from running at 30 fps because it was so poorly coded and made such inefficient use of the cpu to running at 6000 fps because it now completes each loop pass that much faster, the cpu usage is actually the same.

Now if your code is so optimized that it can run at 6000 fps, at that point you can say “gee, I don’t need this many updates a second, let me cap it to x frames per second.” But how do you do that? The GPU is grabbing finished frames out of the buffer at its own pace, whether you are generating them at 6k/sec or just 5/sec. To cap your cpu consumption you would usually say “we need a new frame every 0.015s to always have a new frame ready for the GPU so that the screen updates sixty times a second, so if we finish a frame in 0.001s instead, sleep (effectively yielding cpu consumption to other processes) for 0.01 seconds after we run through the loop” - but while that may work for some things, there are other stuff that need to happen “in real-time” such as reloading the audio buffer (to avoid pauses or corrupted/garbled audio), etc and you also can’t rely on the system to actually wake you before 0.015s even though you asked it to wake you after just 0.01s to be extra safe.

Tl;dr, yes, once your code is running at 6k fps, then capping it to reduce consumption is an option, but running at 6k fps doesn’t actually increase cpu vs inefficiently running at 30fps.

What? Definitely happens, latest when one of the cheaper thinner bottle types have been sitting a bit too long in the hot the plastic taste becomes intense.

And even if below noticing levels I think plastic molecules have been detected in such beverages, but uncertain here.

Glass is amazing. You haven't tasted a beverage until you had it in a glass cup or bottle.