So lets see if they might "save us"

2028 is another story depending on whether this frenzy continues / fabs being built (don’t know whether they are as hard as cpu)

I highly recommend disabling javascript in your browser.

Yes, it makes many sites "look funny", or maybe you have to scroll past a bunch of screen sized "faceplant" "twitverse" and "instamonetize" icons, but, there are far fewer ads (like none).

And of course some sites won't work at all. That's OK too, I just don't read them. If it's a news article, its almost always available on another site that doesn't require javascript.

E.g. IDEs could continue to demand lots of CPU/RAM, and cloud providers are able to deliver that cheaper than a mostly idle desktop.

If that happens, more and more of its functionality will come to rely on having low datacenter latencies, making use on desktops less viable.

Who will realistically be optimising build times for usecases that don't have sub-ms access to build caches, and when those build caches are available, what will stop the median program from having even larger dependency graphs.

A dad comes home and tells his kid, “Hey, vodka’s more expensive now.” “So you’re gonna drink less?” “Nope. You’re gonna eat less.”

The bigger the company = longer the contract.

However it will eventually catch up even to Apple.

It is not prices alone due to demand but the manufacturing redirection from something like lpddr in iphones to hbm and what have you for servers and gpu

SoCs with on-die memory (which is, these days, exclusively SRAM, since I don't think IBM's eDRAM process for mixing DRAM with logic is still in production) will not be effected. SiPs with on-package DRAM, including Apple's A and M series SiPs and Qualcomm's Snapdragon, will be effected -- they use the same DRAM dice as everyone else.