3 ms·

WebStorm too https://blog.jetbrains.com/blog/2024/10/24/webstorm-and-rider-are-now-free-for-non-commercial-use/ https://blog.jetbrains.com/blog/2024/10/24/webs

WebStorm too https://blog.jetbrains.com/blog/2024/10/24/webstorm-and-rider-are-now-free-for-non-commercial-use/ https://blog.jetbrains.com/blog/2024/10/24/webstorm-and-ride...

judge2020 2y ago
This is pretty huge since web technology has always been the “paid tier” for JB products
hbn 2y ago
Oh that's awesome! I'm a huge fan of the JetBrains IDEs - the way it understands code relieves so much mental overhead when tracing through my code, finding usages, refactoring, etc. It's one of the rare pieces of software I actually enjoy using. I just can't justify the cost for personal use for the amount I use it, and the fact that I've never really monetized a side project. Super happy they're making this move. I think there's good logic to getting people hooked with free personal use so they can convince their company to buy licenses for everyone at work.
Timon3 2y ago
Hm... I'm not sure whether this is a good or bad sign. I've been a Jetbrains user & proponent for many years, with most of my usage in WebStorm. But over the last ~2-3 years I've faced more and more bugs, some sitting open for weeks and months. Just for a short selection: - The autocomplete popup sometimes froze the IDE completely (and killing the process caused minutes of data loss), open for close to a year[0] - Since two months ago, the Typescript language server fails to start in Vue projects (due to a broken update by the Vue team). A fixed version of WebStorm was released yesterday, in the meantime you were apparently expected to search for the error message, stumble upon the YouTrack page, and apply a workaround[1] - Performance is abysmal in a larger React MUI project, think 10-15 seconds for feedback on code changes, sometimes errors just stick around for a good minute or more[2] - In some situations WebStorm makes autocomplete suggestions that aren't allowed - think effectively a type T with keys K | L, where Omit<T, K> leads to only suggesting K properties, while removing the Omit makes it suggest both K and L properties - After updating from 2024.1.X to 2024.2.Y, the window had no buttons for minimizing/maximizing anymore. Now, this was partially caused by my environment, but after I found a workaround it was closed as "Third Party Problem". Still feels like a regression to me, since my environment did not change. These are some of the more memorable ones from this year, but it feels like there's a new one every week. I'm pretty close to dropping my subscription, and this news doesn't fill me with confidence that the necessary investments in Q&A will be made. [0]: https://youtrack.jetbrains.com/issue/JBR-6171/Random-freezes-when-code-suggestions-opens-on-New-UI https://youtrack.jetbrains.com/issue/JBR-6171/Random-freezes... [1]: https://youtrack.jetbrains.com/issue/WEB-68756/Vue-LS-2.x-Couldnt-Start-server.watchFiles-is-not-a-function https://youtrack.jetbrains.com/issue/WEB-68756/Vue-LS-2.x-Co... [2]: https://youtrack.jetbrains.com/issue/WEB-59766/Very-slow-code-analysis-in-React-MUI-Javascript-code https://youtrack.jetbrains.com/issue/WEB-59766/Very-slow-cod...
- exceptione 2y ago
  I'm pretty close to dropping my subscription, and this news doesn't fill me with confidence that the necessary investments in Q&A will be made. ... or Jetbrains is trying to get more paying customers in, so they can get these issues resolved.
  - Timon3 2y ago
    That could be the long-term approach, but in the short-term it will only lead to fewer paying customers. It doesn't help me if the issues start getting resolved in 2-3 years - the editor is barely usable right now, and I won't wait another year. And should they actually lose me, I won't be coming back unless they make amazing improvements that are years ahead of any other editors to win.

WebStorm too https://blog.jetbrains.com/blog/2024/10/24/webstorm-and-rider-are-now-free-for-non-commercial-use/ https://blog.jetbrains.com/blog/2024/10/24/webstorm-and-ride...

judge2020 2y ago

This is pretty huge since web technology has always been the “paid tier” for JB products

hbn 2y ago

Oh that's awesome! I'm a huge fan of the JetBrains IDEs - the way it understands code relieves so much mental overhead when tracing through my code, finding usages, refactoring, etc. It's one of the rare pieces of software I actually enjoy using. I just can't justify the cost for personal use for the amount I use it, and the fact that I've never really monetized a side project. Super happy they're making this move. I think there's good logic to getting people hooked with free personal use so they can convince their company to buy licenses for everyone at work.

Timon3 2y ago

Hm... I'm not sure whether this is a good or bad sign. I've been a Jetbrains user & proponent for many years, with most of my usage in WebStorm. But over the last ~2-3 years I've faced more and more bugs, some sitting open for weeks and months. Just for a short selection: - The autocomplete popup sometimes froze the IDE completely (and killing the process caused minutes of data loss), open for close to a year[0] - Since two months ago, the Typescript language server fails to start in Vue projects (due to a broken update by the Vue team). A fixed version of WebStorm was released yesterday, in the meantime you were apparently expected to search for the error message, stumble upon the YouTrack page, and apply a workaround[1] - Performance is abysmal in a larger React MUI project, think 10-15 seconds for feedback on code changes, sometimes errors just stick around for a good minute or more[2] - In some situations WebStorm makes autocomplete suggestions that aren't allowed - think effectively a type T with keys K | L, where Omit<T, K> leads to only suggesting K properties, while removing the Omit makes it suggest both K and L properties - After updating from 2024.1.X to 2024.2.Y, the window had no buttons for minimizing/maximizing anymore. Now, this was partially caused by my environment, but after I found a workaround it was closed as "Third Party Problem". Still feels like a regression to me, since my environment did not change. These are some of the more memorable ones from this year, but it feels like there's a new one every week. I'm pretty close to dropping my subscription, and this news doesn't fill me with confidence that the necessary investments in Q&A will be made. [0]: https://youtrack.jetbrains.com/issue/JBR-6171/Random-freezes-when-code-suggestions-opens-on-New-UI https://youtrack.jetbrains.com/issue/JBR-6171/Random-freezes... [1]: https://youtrack.jetbrains.com/issue/WEB-68756/Vue-LS-2.x-Couldnt-Start-server.watchFiles-is-not-a-function https://youtrack.jetbrains.com/issue/WEB-68756/Vue-LS-2.x-Co... [2]: https://youtrack.jetbrains.com/issue/WEB-59766/Very-slow-code-analysis-in-React-MUI-Javascript-code https://youtrack.jetbrains.com/issue/WEB-59766/Very-slow-cod...

exceptione 2y ago
I'm pretty close to dropping my subscription, and this news doesn't fill me with confidence that the necessary investments in Q&A will be made. ... or Jetbrains is trying to get more paying customers in, so they can get these issues resolved.
- Timon3 2y ago
  That could be the long-term approach, but in the short-term it will only lead to fewer paying customers. It doesn't help me if the issues start getting resolved in 2-3 years - the editor is barely usable right now, and I won't wait another year. And should they actually lose me, I won't be coming back unless they make amazing improvements that are years ahead of any other editors to win.