Somehow, in most other areas of engineering, people know how to reliably make things that last. All mistakes that were ever made are documented and taught so they're never repeated. Yet in software, half of the assumptions consistently turn out to be wrong (yeah, who knew there could be years after 1999) and the quality is severely lacking because "we can always push an update" so everything is in a perpetual beta.
> the resources your code uses are finite and the constraints around the resource usage may change
How? A chat app or a web page has no business using several gigabytes of RAM. About the only thing that I can think of that does push the available resources on modern devices to the limit is AI. Which is very niche and gimmicky, at least right now.
But then yes, it makes sense to update OSes to support new hardware. But only for that. Adding a couple of drivers doesn't warrant a major OS release. Neither does exposing new hardware capabilities via APIs so apps could make use of them. And redesigning UIs just for the sake of it is indefensible, plain and simple.
> the resources your code uses are finite and the constraints around the resource usage may change
How? A chat app or a web page has no business using several gigabytes of RAM. About the only thing that I can think of that does push the available resources on modern devices to the limit is AI. Which is very niche and gimmicky, at least right now.
But then yes, it makes sense to update OSes to support new hardware. But only for that. Adding a couple of drivers doesn't warrant a major OS release. Neither does exposing new hardware capabilities via APIs so apps could make use of them. And redesigning UIs just for the sake of it is indefensible, plain and simple.