4 ms·
> Software is something that needs to be continuously developed and maintained. Not always. Sometimes software is "done" and warrants no further changes or mai
by sangnoir 9y ago
> Software is something that needs to be continuously developed and maintained.
Not always. Sometimes software is "done" and warrants no further changes or maintenance. I have run into this issue with mobile apps that worked perfectly to my satisfaction until the authors decided to "redesign" or "improve" it. I think subscription is a valid use case for customers who want active maintenance, but it should be opt-in. I detest the forced-subscription model that JetBrains attempted ("Didn't pay the latest subscription? We'll brick the application you've installed and are running on your hardware").
- cdelsolar 9y agoDo they actually brick it? I thought they just stopped upgrading it.
- sangnoir 9y agoReposting links I added in another reply. Yes they announced the bricking plans (http://bytecrafter.blogspot.com/2015/09/how-jetbrains-lost-years-of-customer.html http://bytecrafter.blogspot.com/2015/09/how-jetbrains-lost-y...) and then backtracked (https://blog.jetbrains.com/blog/2015/09/18/final-update-on-the-jetbrains-toolbox-announcement/#more-7340 https://blog.jetbrains.com/blog/2015/09/18/final-update-on-t...) - which is why I said "attempted".
- FooBarWidget 9y agoSometimes, sure. But nowadays software is more often than not something that isn't simply done and needs continuous updates, in the face of security vulnerabilities, changing requirements (people using the software for changing use cases), platform updates (new version of macOS or Linux that breaks compatibility), etc.
- s73ver_ 9y ago" I detest the forced-subscription model that JetBrains attempted ("Didn't pay the latest subscription? We'll brick the application you've installed and are running on your hardware")." They never attempted that. You were always able to use the version you paid for, even if you stopped your subscription.
- sangnoir 9y ago> They never attempted that Oh, but they did[1]. You might have missed the initial drama as it transpired because of their quick U-turn (to their credit). I have reason to doubt the subscription plans they published which clearly stated that failure to keep up with the subscription would lead to bricked IDEs. JetBrains only backtracked[2] after receiving sustained pushback. There were HN posts for the initial bricking plan[3] and the backtrack[4]. 1. http://bytecrafter.blogspot.com/2015/09/how-jetbrains-lost-years-of-customer.html http://bytecrafter.blogspot.com/2015/09/how-jetbrains-lost-y... 2. https://blog.jetbrains.com/blog/2015/09/18/final-update-on-the-jetbrains-toolbox-announcement/#more-7340 https://blog.jetbrains.com/blog/2015/09/18/final-update-on-t... 3. https://news.ycombinator.com/item?id=10170089 https://news.ycombinator.com/item?id=10170089 4. https://news.ycombinator.com/item?id=10278285 https://news.ycombinator.com/item?id=10278285