@joe see also, when quartz arrived, people did say "the battery is rubbish" and "you have to get it replaced every month" and "you won't hand it down to your children" and all that remains of the industry is luxury consumerism wheee
@tef hardware-wise, the industry's already been at the point where any laptop or phone from 15 years ago would be physically fine, if not for abandoned software support and soldered-on consumables like battery and ssd. maybe sloppening will cause hardware quality to peak but i would hope that better repairability regulations help with the latter problem. software strikes me as the weak link in us getting to heirloom computers (of course companies don't want to fix that so they can sell new ones)
@whitequark @tef if i was going to sit down and spec out a forever os, i think i'd also want to make sure the components that are the biggest attack surfaces are compartmentalized from the rest of the system, so essential security updates can roll out independent of whether you update the UI parts of your system, so you don't have to take the flavor-of-the-month UI updates or A/B tests just to not get owned. (though i know there's no perfectly clean separation there too)
@whitequark @tef i say "forever" but maybe i just mean at least a decade or so, without frivolous forced expertise-breaking changes along the way
@joe in theory, Rust, or Node with JIT disabled, is another way to get memory safety. It has the advantage that you can audit and patch your security layer if it turns out to be buggy.
Possibly #CHERI will be implemented in microcode, so you can field upgrade without a soldering iron, but, if so, that's not really hardware. It's just software you can't see.