Comment by markus_zhang 4 days ago
Is the Jetbrain model basically the pricing model of early era (pre 2000s) IDEs? I remember back then developers had to pay for editors and compilers, which usually came with a huge amount of manuals. And then they could install patches until a new major version rolled out. I'm actually OK with that model, if they still ship manuals in paper.
I'd like to take a cup of coffee, take out one of those books (not super interested in Oracle TBH but could be some other low level stuffs) and read it through.
OK I know reality is much less appealing than that. But I still prefer paper books than .CHM help files than really online documents.
Yeah, I think it's pretty similar. I definitely remember purchasing copies of the software like Borland C++ / Visual Studio / etc. that would essentially cover the major version number and all patch related updates.
Although personally, I don't know if jetbrains offers an actual physical copy (give me back the big box!).
I love big boxes too! The manuals also show that developers really really know their products.
It sucks that fast iteration is the new normal nowadays. It's not a bad thing if developers are eager to get their hands on a cutting edge feature, but I believe doing things slower but more thoroughly has its merit.
No they did not show that. They showed that the project team for the tools included more than developers.
It included qualified technical writers. It included project managers would would ensure that if somethiung was added there was a specification so that it could be documented.
ie developers were not allowed to get away with only doing a partial job.
I think that's a good thing, developers not allowed to get away with partial job.
Jetbrains originally had a "buy upgrade model". You paid full price for the first one, and then it was half price for upgrades beyond that.
To Jetbrains, this had the problem of feast or famine and the non-predictable income. They'd need to release an upgrade when they needed money and they would hold off on releasing features as a minor release so that they could justify an upgrade later.
At some point (I want to say 2014 based on my licensing), they trial ballooned a subscription only model and got some extreme pushback about it. With that feed/pushback Jetbrains went to the perpetual fallback and subscription. It addresses the subscription issue - they now have a revenue stream rather than the upgrade. It also means that they do a lot of minor releases now with new features throughout the year.
The other part of the perpetual fallback is that if you have a subscription to a version for a year, you will always be able to use that version even if you cancel your subscription. If I canceled my subscription, I'd be able to use IntelliJ 2024.2 forever. I'm currently running 2024.3.3
One other bit on the subscription - it gets less expensive each year. I've got an all products pack for single user. My next yearly billing will be $173.00. https://www.jetbrains.com/store/?section=personal&billing=ye... - the 3rd year and onwards (I've been a Jetbrains used since the end of the world sale - https://blog.jetbrains.com/blog/2012/12/20/jetbrains-end-of-... )
https://sales.jetbrains.com/hc/en-gb/articles/207240845-What...
Related from 2019: https://news.ycombinator.com/item?id=21798033