So the 1970s oil crisis caused a shift that included fuel efficiency rules. For like, the whole time I've been a software engineer, memory footprints of a lot of software have crept up, even when they aren't really doing more. The memory situation currently is a mess. But ... is it bad enough to get us to _change_ how we build?
That would be a great outcome of this situation. I doubt it will happen though: unlike fuel efficiency rules, there aren’t likely to be external pressures like that on software. Outside developer circles most users likely are unaware of memory usage and often just accept that computers are slow and unreliable sometimes. That’s different from drivers who see their fuel gauge and the corresponding cost of fuel, and are…
Wrt. the memory efficiency - considering that AI is going to be the main workload by far and thus will vacuum in majority of the available optimization resources - be it humans or coding AI - i think it will be even less chances that any meaningful resources will be spent on optimizing on the fringe, ie. the users' OS/browser/etc.