Poorly optimised software exist bcoz they know they can leverage on high power CPUS, high power CPU exist bcoz existing hardware uarch are poorly optimised for power efficiency & ipc, poorly optimised uarch exist bcoz back then the 70s & 80s (when X86 was rising), power efficiency wasnt a thing.

AFAIK I havent heard of a poor Apple or Android/Arm software that sucks more power than needed to run it. I stand to be corrected.

For X86 uarch to move forward, it needs to ditch legacy 16bit & 32bit function, and revamp its 64bit compute to be on par with SD/ Mseries.

Intel problem in this tered is symptomatic of X86 limitations due to pushing power limits when they hit the down nodeing wall. AMD 9000series is also indicative of this, perhaps moreso of the future, when they decided to pull back the TDP limit to 65W, as i suspected seeing TPU review with PBO off there was a little 5% more to gain so AMD too have hit a power performance wall with current uarch & node.

Ryzen HS and Core HX CPUS are mobile parts no? But they share the same uarch as desktop parts and these are thermally hard to cool unlike SD Elite.

Just bcoz its not used in Windows doesnt mean the hardware to run is not ady there


But its precisely that since Windows no longer interact at such base algo that it makes no sense to keep them, so why not deprecate and remove 16 & 32bit function. Then by optimising 64bit, the transistor saved can be reuse to improve elsewhere or cut the die size down to reduce cost.

And its not like the end for legacy programs as software emulation could be used to run them.