Earlier quoted context omitted.
> Subscription business models I think a subscription business model is the only honest way to sell software that will require ongoing support. If you're comfortable with a snapshot w/o updates, then by all means buy once, but I think coming to terms with the demands of ongoing support also means coming to terms with continuing to support the product in some way. That said, I wish there were more variations in the wa…
I don't quite see why free bug fixes/minor features + paid major upgrades model should be any different from subscription model for developers, except giving the users control over when to upgrade. Control that is essential for apps that contain critical data. BTW, I think they do have an option that you pay for 3 years upfront. At least, that was one of the options they mentioned when I complained about the lack of…
I know that it's very common for subscription models to coincide with forced upgrades (as this one does), but that seems like a choice on the part of the company as opposed to something inherent to the revenue model. I'd be quite happy to pay a developer to continue to maintain an older version of their software.
Like you pointed out, I think a fee structure where you pay for major updates and otherwise pay a maintenance / hosting subscription fee makes the most sense.
I think that you see open source projects that struggle along all of the time because their developers cannot afford to work on them enough. Not every project, but enough of them. I try to support projects like that too.