> All they need to do is drop the being locked out of your project after twelve month and it would be fine.
>
> I mentioned somewhere else on these forums that I have a suite of components for UI dev in VS which is a twelve month sub type system. But if you don't renew the sub you can't get updates, additions. or bug fixes - you do however get to keep and use the components forever after that. Additionally you can renew your sub at any time you want - even years later - at a reduced price.
>
> I can renew it now if I want, although I haven't done so for nearly two years, because there is nothing new added that I need.
>
> This way you are not milking them by expecting never ending work done to the tools, and they are not milking you by expecting you to keep paying to use the tools.
>
> Much fairer system I think.
>
The problem with that idea though is that you would indeed still be milking them, since you don't pay to keep the server running anymore, yet you still have access to it. At some point there wouldn't be money to pay for the cloud server anymore without a loss because nobody would be paying annually, yet their server would possibly need upgrades because of a larger user-base that would require a bigger server capacity and other things.
If you are a corporation with other products that are profitable, then yes it's possible but if you're a company with a one time fee product, then there's no steady income to make such a business model possible.
You may not have access to the cloud anymore, but you can still download your stuff and work offline as far as I have understood.
This is why they should launch with the desktop version. I wouldn't even consider it if it's going to be purely internet-based saves and browser-based work. To be honest, I've skipped over all this, it doesn't make any sense to me. Isn't that stuff usually for applet-type tools?