Earlier quoted context omitted.
Nobody gets paid to leave things alone and maybe that's a big problem with the world.
It's definitely a big problem with software. This "need to constantly pay developers" is part of the justification for moving towards subscription payment instead of one-time payment. The logic goes: One-time payment won't pay for future changes, and developers are always making changes, and they need to be paid for. But, what if I don't want future changes? For almost all software I've ever paid for, as a user, I ju…
Problem is, most software doesn't exist in a vacuum; it is part of an ecosystem. Security updates that you might pay for are not enough, because the ecosystem is constantly changing around the program you bought.
I'm author of HashBackup. It uses remote object storage services so if there are incompatible changes made on the storage side, the software has to adapt. What if IP4 is no longer supported? Adapt. A library like Boto2 gets rewritten and the old version loses support. Adapt. Google Sites decides to force you to migrate to a new version that looks like shit. This just happened to me, and it's so bad I'm having to do a whole new documentation site.
Just keeping software working has become a big challenge because of ecosystem changes.