Hacker News new | ask | show | jobs
by gorohoroh 3938 days ago
Let's discuss. Why do you think this is bad?
5 comments

I don't like the idea that my IDE is a tool that will stop working if I stop paying the ransom for it. This model may be the future, but it's a very icky feeling that I can't purchase to own software that runs entirely on my desktop, since that's been the model for YEARS.

Paying annually for support and to receive upgrades feels very reasonable. My IDE ceasing to function because I've stopped paying annually does not.

Not the OP, but I'm also not really a fan of subscription model of any software products even though I'm OK with paying for upgrades every year. With subscription model I no longer own the software the moment I stopped paying, even if I already paid monthly fee to equivalent of perpetual license pricing.

But on the other hand, considering I'm already paying $158 for two of their products every year (IDEA and AppCode), being able to pay $149 (discounted rate) and also get a separate app for RubyMine and PyCharm seems like a very nice offer. (Since Ruby/Python plugins in IDEA always lacked few versions behind.)

Nevertheless, I'm sad that to see another one of my most-used software goes away from perpetual license to subscription model.

It's no longer a product - it's a service.

Good examples of the way to do this, include Cakewalk and Allegorithmic which both implement a form of pay-to-own. After enough payments, you own a product that you can keep using if you no longer need 'enhancements'.

Whilst software-as-a-service is great for many people, it's not a panacea and certainly not a replacement for people who just want a product that they buy once and can use when they like without further outlay.

Because right now, we can pay a one time fee and use the software as long as we want, without incurring any more cost in return for not getting updates or imposing a cost on JetBrains.

However, from November, that will no longer be possible. If Jetbrains decides, in 2016, to increase the license fee to $300 per year, or $500, then we will have 2 options: Pay it and continue to have access, or don't pay, and lose all access to the tools, despite the fact that we have already given you money. If I have a cashflow problem, I can no longer decide to stay with last year's version for a while, instead I lose access.

I'm sure you know this, I'm sure everyone at JetBrains knows this.

If Jetbrains decides, in 2016, to increase the license fee to $300 per year, or $500,

Or even more likely (for an IDE that is ahead quite a lot): charge the same license fee, but don't supply any interesting new features.

This is one of my fundamental objections to the subscription model. In the perpetual license model, a company has to entice its customers every major version to shell out the money. How do you do this? By making the product even better. In the subscription model, that direct incentive is gone, the customer has to pay anyway.

JetBrains admit as much in a comment on their blog:

> On the other hand, we think we’ll be able to concentrate on quality more than trying to impress users with new features so they buy upgrades. Our products are more than feature-full and we believe the quality is something that can always be improved.

Translation: We've run out of things that we think you'll actually want to pay for, so we've decided to force you to pay instead.

It's really a shame :(, there's a lot of things that I can still think of, such as a decent Java profiler, a feature competing with JRebel (or far better DCEVM support), etc.
The license seems to say that if you stop paying, you can still use the most recent version as of when your subscription expired. So technically you could subscribe for one month, get the software, and keep using it until you saw a version that was compelling enough to upgrade to.
That's the old licensing model: you had a perpetual license and 1 year worth of upgrade, you could buy more upgrades but if you didn't the last available version would keep working forever.

The whole point of the licensing change and the switch to a service is to remove the perpetual license. No money, no IDE.

That's not how I'm reading it, and I'd be amazed if that was the case, because then, you literally could pay £6 and get PHPStorm to use forever.
That's according to a post earlier in the thread from the guy I presume is from JetBrains. It's also similar to the license Epic had for Unreal Engine, before they got rid of the monthly fee.
You seem to be conflating the perpetual licence, which is what we have currently and will stop being available in November with the new subscription. If I do not move to the subscription model, I can continue to use my current version of PHPStorm, in perpetuity.

However, I cannot subscribe under the new terms, and keep using the software if I decide to stop subscribing. Earlier in this thread you suggested that we could subscribe for a month and keep using the software afterwards. This is incorrect. Once you stop subscribing, you lose the rights to use the software

This is the licensing model that's used now, not the new one introduced in November.
Peace of mind is a really important feature you are discarding with this model.

Not every compelling feature is implemented with code.