My pet theory is that every software product has a "peak version". Before that peak version, the product is not yet in a complete state, and it is fairly obvious, both for the developer and user, what features are missing. Once the peak version is reached, new features are not added because they improve the product, but to justify selling the product again to existing customers, and to 'keep the team busy'. Instead o…
Subscription model is actually way better if you don't want to end up with feature bloat. Because you actually get money from users even if you only ever fix bugs and improve performance. If you freeze your features you will soon arrive at a point where everybody who wanted your software bought it and then the revenue stops.
A decent middle ground is permanent fallback versions. But then you still have the issues with feature creep.