The tradeoff has almost exclusively been development time vs resource efficiency. Very few devs are graced with enough time to optimize something to the point of dealing with theoretical tradeoff balances of near optimal implementations.

▲

pron an hour ago | parent [-]

That's fine, but I was responding to a comment that said that RAM prices would put pressure to optimise footprint. Optimising footprint could often lead to wasting more CPU, even if your starting point was optimising for neither.

	▲	zamadatix 13 minutes ago \| parent [-]
		My response was that I disagree with this conclusion, not that I'm changing the premise. If the starting point was optimising for neither it's VERY easy to optimize one without tanking the other, there's just no pressure to do so at the moment. What you're saying only makes sense if apps were RAM bloated because of algorithmic tradeoffs. If you look at bloated apps, it's because of selecting extremely high level abstractions which are quicker to develop with. E.g. the web based implementation of the Start Menu in Windows 11 is not faster just because it uses more RAM, but it is waaaay easier to develop for.