Comment by cosmic_cheese
21 hours ago
One-time purchase software would become dramatically more sustainable if platform churn could be ground to a halt. Most types of software achieved peak usability and functionality somewhere between 5 and 25 years ago and there wouldn't be much reason for anybody to upgrade if their one-time purchases continued to work in perpetuity. A substantial number even prefer e.g. Word 2000 or Photoshop CS1 over their modern incarnations but can't use those for either technical or legal reasons.
Instead, the reverse has happened and platform churn has risen to new highs, necessitating subscriptions.
Maybe we should just freeze development in lots of designated areas and declare victory (I know this isn't a practical suggestion, but still...).
Eg in desktop OS's. Apple for example makes everyone miserable by re-breaking macOS every year. To what point?
Apple certainly churns APIs quite often. And now my Tahoe install has broken window management, one of the most core features of a modern OS
nvi hasn't meaningfully changed in almost 20 years. It's OK for software to be finished.
Yesterday's submission explained the choice of subscription precisely due to the need if ongoing development: https://news.ycombinator.com/context?id=46716385
Part will be for new features, but no doubt that another big part will be for platform support over time. There's just too little backwards compatibility guarantees nowadays from the big players. We need more Microsofts in that sense!
> Instead, the reverse has happened and platform churn has risen to new highs, necessitating subscriptions.
... Even for desktop Linux users? I can't say I've felt it. I switched almost 4 years ago and it just keeps feeling better and better (in a "Luigi wins by doing nothing" kind of way).
Linux desktops (not the kernel) are actually among the worst when it comes to platform churn. It's one of the reasons why Flatpak, AppImage, Snap, etc require relatively complex machinery and runtimes and whatnot to function. The churn is just masked by package managers.
It's come across to me so far that this just results from application developers targeting a specific DE and not really thinking about compatibility, or even really whether they need specific functionality provided a specific way.
Would be nice to see the XDG stuff like portals etc. better respected, though, yeah.
2 replies →
if snaps were masked by apt, there wouldn't be such an objection to them.