3 ms·

They are not 'all in' on the subscription model: if you stop paying you still get to use the last version issued while you were a subscriber. (Or maybe the one

by atleta 4y ago

They are not 'all in' on the subscription model: if you stop paying you still get to use the last version issued while you were a subscriber. (Or maybe the one that was the current one when you paid your yearly subscription, but it doesn't make much of a difference.) They call it 'perpetual fallback license'. I think it's a fair compromise between owning what you have paid for and being able to fund continuous development of the platform (and also to be able to receive updates without having to make a buy/skip decision all the time). Also, they are not a Russian company and have severed ties with Russia a few weeks after the war has started.

nightski 4y ago
Yes if you stop paying you need to downgrade to the version at the time of payment, probably from a year ago. It can make a big difference if the ecosystem is changing. For example, in .NET if you are using a newer version of .NET at that time it could make the IDE unusable. I have been using their products for over a decade but I still hate this model. Typically when buying a full product + support subscription you are supposedly paying for bug fixes/enhancements that come during that support period - it's built into the price.
- atleta 4y ago
  I've checked their website [1] and it says that the fallback includes bug fixes during the period you've paid for. Yes, 1 year can make a difference, but I see the fallback as a way of being able to have the product around just in case I need it after deciding I don't need it enough to continue paying for it. Sure, if .NET (or whatever your platform of choice) gets updated during your last subscription period, that may seem like bad luck. But sooner or later it will happen anyway and thus it will affect you if you stop paying. (Not sure about how .NET works, but in the java world, especially on linux, you can have multiple versions installed, so you could still continue using the product.) Another way to look at it is that when you first buy the product, you pay for that version and you get temporary access to updates during the next year. Then you buy the next version and get temp access for the updates to that one for another year. So looking at it from the first payment it makes sense. But I agree, that what you say would be more elegant and probably also easier to digest/understand. [1] https://sales.jetbrains.com/hc/en-gb/articles/207240845-What-is-a-perpetual-fallback-license- https://sales.jetbrains.com/hc/en-gb/articles/207240845-What...
  - pseudalopex 4y ago
    > I've checked their website [1] and it says that the fallback includes bug fixes during the period you've paid for. It said bug fix updates. Many bug fixes are in feature updates.
  - nightski 4y ago
    I understand how they want you to look at it. I just hate it as it seems really petty. It really turned me sour on them. Like I said, I've been a customer for over a decade.
    - atleta 4y ago
      I don't know what they (or others) want, it's just how I interpret it.
- deleted 4y ago
  [deleted]
LelouBil 4y ago
Also, their Early Access Preview builds for major releases are free

by atleta 4y ago

nightski 4y ago

Yes if you stop paying you need to downgrade to the version at the time of payment, probably from a year ago. It can make a big difference if the ecosystem is changing. For example, in .NET if you are using a newer version of .NET at that time it could make the IDE unusable. I have been using their products for over a decade but I still hate this model. Typically when buying a full product + support subscription you are supposedly paying for bug fixes/enhancements that come during that support period - it's built into the price.

atleta 4y ago
I've checked their website [1] and it says that the fallback includes bug fixes during the period you've paid for. Yes, 1 year can make a difference, but I see the fallback as a way of being able to have the product around just in case I need it after deciding I don't need it enough to continue paying for it. Sure, if .NET (or whatever your platform of choice) gets updated during your last subscription period, that may seem like bad luck. But sooner or later it will happen anyway and thus it will affect you if you stop paying. (Not sure about how .NET works, but in the java world, especially on linux, you can have multiple versions installed, so you could still continue using the product.) Another way to look at it is that when you first buy the product, you pay for that version and you get temporary access to updates during the next year. Then you buy the next version and get temp access for the updates to that one for another year. So looking at it from the first payment it makes sense. But I agree, that what you say would be more elegant and probably also easier to digest/understand. [1] https://sales.jetbrains.com/hc/en-gb/articles/207240845-What-is-a-perpetual-fallback-license- https://sales.jetbrains.com/hc/en-gb/articles/207240845-What...
- pseudalopex 4y ago
  > I've checked their website [1] and it says that the fallback includes bug fixes during the period you've paid for. It said bug fix updates. Many bug fixes are in feature updates.
- nightski 4y ago
  I understand how they want you to look at it. I just hate it as it seems really petty. It really turned me sour on them. Like I said, I've been a customer for over a decade.
  - atleta 4y ago
    I don't know what they (or others) want, it's just how I interpret it.
deleted 4y ago
[deleted]

LelouBil 4y ago

Also, their Early Access Preview builds for major releases are free