Software is something that needs to be continuously developed and maintained. Charging a one-time fee is a fundamentally unsustainable approach. We all have to face reality and start paying for software as a subscription.
Now, that will likely end the bubble of "I can buy 100 apps, most of which I'll never use", which we have been in for the last 20 years or so. But perhaps the few apps that people will pay for will become better as a result. I'm hoping for it.
> Software is something that needs to be continuously developed and maintained.
Not always. Sometimes software is "done" and warrants no further changes or maintenance. I have run into this issue with mobile apps that worked perfectly to my satisfaction until the authors decided to "redesign" or "improve" it. I think subscription is a valid use case for customers who want active maintenance, but it should be opt-in. I detest the forced-subscription model that JetBrains attempted ("Didn't pay the latest subscription? We'll brick the application you've installed and are running on your hardware").
" I detest the forced-subscription model that JetBrains attempted ("Didn't pay the latest subscription? We'll brick the application you've installed and are running on your hardware")."
They never attempted that. You were always able to use the version you paid for, even if you stopped your subscription.
Oh, but they did[1]. You might have missed the initial drama as it transpired because of their quick U-turn (to their credit). I have reason to doubt the subscription plans they published which clearly stated that failure to keep up with the subscription would lead to bricked IDEs. JetBrains only backtracked[2] after receiving sustained pushback. There were HN posts for the initial bricking plan[3] and the backtrack[4].
Sometimes, sure. But nowadays software is more often than not something that isn't simply done and needs continuous updates, in the face of security vulnerabilities, changing requirements (people using the software for changing use cases), platform updates (new version of macOS or Linux that breaks compatibility), etc.
Quite honestly, I don't mind paying a subscription for updates. But I detest having to pay a subscription when all I want is a single copy and don't require rolling updates and support.
Charging a one time fee works just fine for lots of folks out there making software. It's especially good for anyone who's doing it in their spare time as they don't have to provide updates for every little niggle someone may find. Some offer a subscription alongside the one-off model, which is the best of both worlds if the developer(s) are continuously working on it. Others ask you to purchase the major upgrades but give minor upgrades for free.
There are lots of payment models out there, and the developers should pick what works for both them and their customers. There's no way most of my colleagues who have a license would have purchased sublime if it was a rolling cost, so that model seems to be working in their favor right now, at least for single developer purchases.
Software is something that needs to be continuously developed and maintained. Charging a one-time fee is a fundamentally unsustainable approach. We all have to face reality and start paying for software as a subscription.
Now, that will likely end the bubble of "I can buy 100 apps, most of which I'll never use", which we have been in for the last 20 years or so. But perhaps the few apps that people will pay for will become better as a result. I'm hoping for it.