https://youtrack.jetbrains.com/issues?q=by:%20albertzeyer%20
I don't want to sound too negative here though. In general, I'm very happy with IntelliJ, and I think it's currently the best available IDE for many languages (I care mostly about Python and PyCharm currently).
https://youtrack.jetbrains.com/issue/IDEA-256708
- Regression: Markdown preview vertical sync does not work anymore
- Makes editing long documentation files a pain, I have to use an external markdown editor now
- First reported 12 months ago
https://youtrack.jetbrains.com/issue/IDEA-282427 - Regression: Git actions don't work anymore when looking at the file diff window
- Breaks my reviewing workflow, I have to use an older version of IntelliJ (which of course has its own problems)
- First reported 3 months ago
Missing / incomplete features is one thing (hello Scala 3 support), but leaving regressions unfixed for so long is breaking the fundamental trust that users have in your product – the ability to rely on the basic functionality that already exists.This kind of bugs should be utmost priority, because they directly impact the cashflow.
While VS Code has great WSL2 support, IntelliJ IDEA can not even show proper error messages when opening Maven projects inside WSL2.
If some text is highlighted, the Ctrl-Shift-F dialog will populate with that text, and it will be focused and selected.
If nothing is highlighted in the editor, then it uses some random bit of text from the search history buffer, and does not focus the input.
[1] See this highly voted issue: https://youtrack.jetbrains.com/issue/IDEA-186988 (opened since more than 3 years already)
I used to like Intellij but got fed up and just stopped using it. Dealing with regression bugs isn't worth it. An IDE should be extremely stable, releasing new features is great but it shouldn't be to the detriment of existing features.
5. Do you fix bugs before writing new code?
Over the weekend I spent a good chunk of a day fighting with a copy of Windows 11 for ARM preview that has a major bug wherein the Start Menu just straight-up doesn’t work. I’m not sure Microsoft is running at 12 full-time 21 years on from when this article was posted.
Disclaimer: I know that the above is an oversimplification but the point is there has to be a balance between fixing bugs and adding features. You can't wait until all reported bugs have been fixed.
True
> It's usually harder to attract new customers
To my defense that difficulty was factored in the 2% figure.
Stability and bug fixes is not sexy and I believe underestimated as a way to retain customers but it's critical to customer happiness.
Like the OP I've simply stopped reporting bugs, because they don't get looked at for literally years, let alone fixed.
The product is OK-ish, the support is abysmal.
I’m still paying for IDEA Ultimate, but it's only because I’m waiting for a better IDE with a more fair subscription system (when I cancel the subscription that was at least 1 year long, I should have the LATEST version I’ve paid for, not the first one). I will try Feet, of course, but I have no high hopes nor trust for JB.
So personally I'm willing to extend some trust to IntelliJ.
As a product it's quite pleasant to use. For Java development it strangely lacks quite a few of the nicer features of Eclipse, but its good quality support for so many different languages (e.g. for Rust) compensates for that.
I also bought new hardware - and noticed no real improvement (something about a fundamental threading problem, I think).
About 6 months ago I was finally fed up and just accepted I would be slower and less productive in some areas for a while without ReSharper, but that it would be OK.
I still miss features from it on a daily basis, but overall I am now quite happy with vanilla VS2019/22 - and never want to go back to the lag-hell that is ReSharper.
As for refactorings and analyses: Roslynator is quite nice, but requires some tweaking which rules you really want enabled because it will otherwise cause lag as well.