I don’t understand how this is getting approved.

Because you get promoted for changing things, not for keeping things the same. Almost every change like this is motivated by someone trying to get promoted.

It seems silly to be distrustful of proprietary BIOS firmware without having the same skepticism of the actual hardware.

I had a linux 5520 and it was terrible. Standby and bluetooth never worked properly. Are the new models any better?

I think it’s more like “snuck up on us” than any kind of nefarious connotation. Kind of like “how did a niche game like BG3 sneak into the top ten games list”?

That’s why your phone has a brightness slider, or better yet an ambient light sensor that automatically adjusts brightness. DE will need something similar.

It’s entirely possible that the translation layer will alter timing to expose a race condition such that something doesn’t render.

I blame Linux distros for being too complicated and unintuitive for 95% of the population, which in turn gives it a negligible market share from a game development perspective.

Or just sync before pulling it.

Diablo Immortal is 18GB.

weirdly high cost

Price is completely independent of cost. Products are almost always segmented into three tiers. The lowest tier enables breadth and is sometimes sold at a loss. Middle tier is where most money is made, by having vastly higher margins. High tier is mostly to capitalize on people with money to spare, and to provide a psychological boost to the middle tier so those people think they’re making a balanced choice.

This is how all consumer electronics are priced.

The problem is that only half of the chiplets have access to the large cache. If the scheduler isn’t aware of that and a lot of data is shared across cores (as in the case for many games), you’ll miss out on most of that performance. AMD wrote a driver for Windows to help optimally schedule threads with high cache intensity to the expanded cache chiplets, but they didn’t do it for Linux. If your workload is not very chatty between cores, and threads don’t need to synchronize at 60Hz, it won’t matter as much. But for game workloads, it makes a big difference, and can actually result in worse performance than the homogenous chiplet design of the mid-tier 7800X3D if you get it wrong.

That’s kind of my point. Linux supports it, but Windows doesn’t anymore. Why? Money - OEMs aren’t selling them anymore, so why spend time to support new features on them? On the flip side, the heterogeneous chiplet structure of the 7950X3D was supported on Windows from day 1, while on Linux the scheduler is still unaware of the different perf characteristics to this day. Why? Same answer - money. AMD doesn’t make money selling 7950X3D on Linux, so they’re not going to spend time writing a kernel driver to optimize perf on it.

I hate to break it to you but 4 years old is nowhere close to “bleeding edge” when it comes to PC hardware.

Linux has better support for the long tail of hardware. Windows has better support for bleeding-edge hardware. The main reason for this is money.

I game … regularly and have never had a driver bug

Presses X to doubt…

If the client is blocking OS fingerprinting by returning generic navigator.appVersion and userAgent values you should probably just assume Linux in the first place.