Total disappointment of your QA at WebStorm
Hello!
I pay for Webstorm license for about 5 years already. I program with Typescript & React on Mac, previously Linux. Your software is getting worse and worse, and I am reaching a point to resign from Webstorm, and even commit to Visual Studio Code to develop some features which I miss there, and they block me from switching. It is open source so at least I do not need to pay for it afterwards.
I really see bugs which I meet multiple times per day in normal usage which are not fixed for years. One example: “Suppress with @ts-ignore” is often being put in a wrong place. If you miss this, then I don't believe there are any people at IntelliJ really using it for daily programming in Typescript.
I also feel like your new features are really buggy, and you totally miss 100% unit test coverage. I personally do not believe even in 80%. It has happened multiple times for me that Webstorm just was hanging.
My proposition: I can stay with Webstorm and report bugs while I do my daily work with Typescript & React if I will be paid for it as your contractor e.g. paid for each reported issue which is not a duplicate.
Kamil Neczaj
请先登录再写评论。
Hi Kamil,
Thank you for taking the time to write all this out — and for being with WebStorm for so many years. We’re sorry to hear how frustrating your experience has been lately. We’d like to follow up with you properly and talk through what’s been happening. Would you be open to continuing this conversation over email? You can reach me at natalia.soshenko@jetbrains.com, or let me know the best way to contact you.
Thanks again for your honesty.
In my company we have hundreds of WebStorm licenses purchased, but more and more are being dropped because performance keeps getting worse with every update. At this point it’s practically impossible to work with medium-sized NX monorepos, even when excluding more than half of the folders from indexing.
Instead of fixing the core issues, you keep adding AI features and addons that we don’t need, while the basic problems remain unresolved. Personally, I’m running out of patience: if the situation doesn’t change soon, I will do the same as many of my colleagues and switch to VS Code.
And not to mention the latest update with Copilot — running the linter or TSLint automatically takes more than 3 minutes with Copilot enabled, even with autocomplete turned off. That’s just ridiculous and unacceptable for a professional working environment.
I can confirm the performance issue too. This might not really be the problem, that some stuff takes longer time, but that it blocks the UI totally. I see at VCS, that some background process have delay of 1-2 sec, but there is no slowdown on UI visible so I can continue coding. At Webstorm, in this time I need to wait, and it distracts a lot. Programming is about being focused, and the focus is great in something called a state of flow. Any distractions here like a 1 sec break to wait for code formatting (sic!) or even very weird AI completion totally not aligned to the context are very distracting and taking programmers out of the flow state.
BTW here is also a good point about how WebStorm (and I guess other IDEs of IntelliJ) are usable at the moment:
https://www.reddit.com/r/Jetbrains/comments/1fzrvkd/webstorm_has_degraded_to_becoming_unusable_for_me/
https://news.ycombinator.com/item?id=43850595
Hello Celoman,
Thank you for sharing your feedback, though it is quite sad to hear that performance issues make users stop using the IDE. Currently, performance is one of the main priorities for our team, which is why we would greatly appreciate it if you contact us via YouTrack and share your diagnostic data(IDE logs and CPU usage snapshots as the first step). This will help us investigate your specific case, particularly in relation to working with an NX monorepo.
As for GitHub Copilot, since it’s a third-party plugin developed and maintained by GitHub, our ability to influence its behavior within the IDE is very limited. However, this case is also worth investigating, and we’ll need the same diagnostic data to proceed.