Live data from Hacker News

How JetBrains Lost Years of Customer Loyalty in Just a Few Hours

bytecrafter.blogspot.com

101–110 of 507 posts

Re: How JetBrains Lost Years of Customer Loyalty in Just a Few Hours

#101

I always hoped that one of these let's force everyone into software subscriptions -actions would become such an embarrassment that companies will think twice about doing this. Given how much I like IntelliJ (and liked JetBrains until they pulled this off), I'd be a bit sad if they would be that example. I am still hoping for a quick follow-up announcement that they have listened to their customers and decided to keep…

I'd point out that "software subscriptions" and "software keeps working even if you don't pay" can both be in place.

For something like this, it's not a half-bad business relationship; the incentives are well aligned for everybody.

For something as fundamental as build software, I'd be nervous about committing to anything where whether I can use the software I already have in two years is in somebody else's hands. I really want to be able to squirrel away complete build environments and know I can build the thing I sold two years ago again if I have to release a "my business may die if I don't" update. Remember, in two years, the "somebody else" may not exist to give me permission. Then what?

The incentives here aren't so good if access to the software is actively being removed for non-payment... the vendor is extracting small values from their customers by forcing their customers to take hidden, but actually quite staggeringly enormous, business risks.

Re: How JetBrains Lost Years of Customer Loyalty in Just a Few Hours

#102
post #66

What bugs me about this is when I asked them about the change on Twitter and they kept trying to blow smoke up my butt about how it's better for everyone. Their first response was that it's cheaper than before. Except it's not. Did they think I wouldn't actually go look at the prices? Then they said it's better because you can jump in and out at will. Only need Product X for a month? Only pay for a month. Which is fi…

> Their first response was that it's cheaper than before.

It is cheaper if you are using a number of their products. It's the same price for the individual products I'm currently using. Net for me is that it's cheaper.

> Which is fine, except I've never heard of a developer who would do that.

I don't code in Python or Ruby every day, but when I do, it's usually for a specific project, and having PyCharm or RubyMine at a low price point and in an environment that I'm familiar with is nice to have. I wouldn't want to buy the IDE outright, but the lower price point is more attractive.

Re: How JetBrains Lost Years of Customer Loyalty in Just a Few Hours

#103
Everyone I've talked to wanted a slight pricing model change with JetBrains, myself included, but nobody wanted a subscription service.

It is just that, often you find yourself wanting PHPStorm, and PyCharms, but that's it. A simple buy one-full-price-half-off-second scheme would have got people like me to say, "yeah sure, let's buy up PyCharms this weekend. Why not?"

Re: How JetBrains Lost Years of Customer Loyalty in Just a Few Hours

#105

Earlier quoted context omitted.

It's my personal opinion that one only gets complaining rights if one doesn't use Gmail, one doesn't subscribe to NetFlix, one doesn't use Spotify, ad nauseum. That does not make sense. Spotify et al. were like that from the beginning. You know what kind of deal you are getting. JetBrains is changing the rules of the game completely, with very little heads-up time, for people who might be deeply invested in their pro…

How exactly do you think more "heads-up time" would improve the situation? Either you are gonna stick with JetBrains and their product, in which case heads-up is irrelevant, or you are gonna switch to a competing product, in which case heads-up wouldn't help either: you will still need to learn the new product, regardless of when you switch .

> How exactly do you think more "heads-up time" would improve the situation?

The delta would be marginal. People just love to complain about change.

Re: How JetBrains Lost Years of Customer Loyalty in Just a Few Hours

#106

Earlier quoted context omitted.

Where JetBrains went wrong is in spreading themselves too thin on too many development fronts, letting products like IntelliJ languish with few significant features added and far too many bugs unfixed, and then deciding the solution to a lack of effort on these products was to switch to a subscription model so that all of their customers would pay for the updates whether or not they're worth paying for.

It seems to me that where JetBrains went wrong was building every language supported as a separate application. According to their announcement post the stated goal of was to deal with the customer ask to get easier discounts on multiple language products or to move from one language to another more easily. To JetBrains the solution was apparently to switch to SaaS, which kind of makes sense, but from my perspective…

The Ultimate version of IDEA seems to support all languages at once.

Re: How JetBrains Lost Years of Customer Loyalty in Just a Few Hours

#107
I purchase a lot of commercial IntelliJ/WebStorm licenses for my company. Previously, the cost was $499/y for new employees, $299/y for existing employees. Now it looks like it will be a flat $319/y for everyone. Eh, I'm OK with that. Now there's also upfront volume discounts, whereas previously you had to talk to sales. In some ways it's simpler for me, and the pricing is in line with other per-dev SaaS costs we have. Consider what you pay for a software Engineer and the productivity gains, personally it's a no-brainer for me. It's the best Java, Scala, Python, JavaScript etc. IDE by far.

With this change, I hope JetBrains takes the opportunity to switch from the big-bang yearly releases to just a continuous stream of improvements. In some ways they've already been moving in the this direction, they've added some pretty great improvements to point releases this year (React/JSX, TypeScript etc. comes to mind). This will eliminate release timing anxiety on both sides (customers optimizing when the best time to buy is, and JetBrains deciding if releasing major new functionality now vs in the next big-bang release), and lets the company ship improvements as fast as possible.

Re: How JetBrains Lost Years of Customer Loyalty in Just a Few Hours

#108
The whole post feels like someone took away the "free lunch". C'mon, we can understand the need to find a business model that works, right? I am having a hard time believing that they're changing just for the heck of it.

Besides, They have a free version of IntelliJ, making the ultimate edition and other languages (for which there are probably more, and free, alternatives) support as "premium".

If their tools are that good, maybe they're worth the money and $119 per year sounds pretty much like peanuts for anyone that is trying to make money.

Re: How JetBrains Lost Years of Customer Loyalty in Just a Few Hours

#109
This isn't even Software-as-a-Service. Most companies that offer SaaS are HOSTING the software and thus incurring ongoing monthly costs. The Service part is that the purchaser doesn't have to install the software on their own machines, pay for nor update servers, etc. Selling rights to use [but not own] software on a monthly basis should be called RtpS - Rent-to-pwned-Software (cause you're pwned, you'll never own it)

Re: How JetBrains Lost Years of Customer Loyalty in Just a Few Hours

#110
As someone managing a small software edition company and selling yearly subscription licenses, I can totally get their business decision. Otherwise, you get the "Microsoft Word 97" effect, when people still use the same old software for 15 years, never upgrade, and complain about your software.

Having a recurring revenue is the best way to be able to manage a company, because it gives you a better view for your next years' budgets, and you can more easily plan investment and hirings.

What is wrong, is probably how jetbrain seems to change their pricing and businell model far too often, lacking direction, and pretending it's for the customers (it's only very indirectly for the customers benefit). Besides, I wouldn't mind paying whatever they want if they would just improve their release quality so that I don't get afraid of breaking my project everytime I update.

Post reply on HN