IntelliJ IDEA along with the platform is the largest team at JetBrains and we're constantly working on bugs and features. If you can please point me to the issues you're referring to in YouTrack, I can check the status.
- 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
- 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 bug is quite telling: https://youtrack.jetbrains.com/issue/IDEA-276949 It is marked as fixed but it is not yet released. If you look inside, you will see that HTTP Proxy authentication has been broken for almost a year. Many corporate users are behind such proxies, and they suffer.
This kind of bugs should be utmost priority, because they directly impact the cashflow.
I think that it would be good to dedicate a few months with no new feature and just focus on fixing all the regression bugs, there's a lot of bugs that are reported for many months to a year seemingly without activity.
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.
That might indicate a good place to work for a software engineer, but not necessarily a profitable business. If a bug affects 1% of your customers but a feature will potentially bring 2% more customers, the business will obviously prioritise the latter.
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.
I think that's often the reasoning behind this but I think the oversimplification doesn't help. It's usually harder to attract new customers than to retain them so retention is important and regression bugs affect that. They slowly erode the confidence until the customers who were your major advocates now become strong critics wherever they go.
oh yes, I didn't mean to harp on you, what I meant is that I believe a lot of executives make the same calculation, oversimplifying things in the same way which leads to the repeated QA issues both Apple and Microsoft have or to the issues that Jetbrains has. New features are exciting and are seen as ways to get new customers.
Stability and bug fixes is not sexy and I believe underestimated as a way to retain customers but it's critical to customer happiness.
> A score of 12 is perfect, 11 is tolerable, but 10 or lower and you’ve got serious problems. The truth is that most software organizations are running with a score of 2 or 3, and they need serious help, because companies like Microsoft run at 12 full-time.
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.
More effective would be to send the board and the CEO links to this and the other thread to show how long-gone the days of "develop with pleasure!" really are.
People on this issue[1] have been asking themselves the same questions.
New very specific features are added with every new releases. However, the Git/shelf experience is lacking the ability to commit specific lines.
This is pretty unrelated, but it's bugged me for years and this is the first chance I've had to ask someone who works at Jetbrains, so I'm going to ask anyway: what exactly is going on with the name "IntelliJ IDEA" versus the other IDEs (Pycharm, RubyMine, etc.)? When I first saw it, I assumed that either "IDEA" was a brand of IDEs of which IntelliJ was one, or the reverse, but I was surprised when I saw that the other IDEs from Jetbrains don't use either word for their names. Is there any other IDEA other than IntelliJ? Is anything else "IntelliJ" besides "IDEA"? The best explanation I can come up with is that there was originally an idea (pun intended) to reuse branding across them, but it was abandoned by the time the other IDEs came out, but I have no idea if this even fits the timeline of their releases, let alone if it's accurate.
It’s funny because I use Rider for work and I did have few issues that I reported but my experience is totally different. I got instant help in every case, usually developer jumping into the thread and people actually fixing bugs.
Sorry for hijacking this question but I thought this might be a chance to push a bit the attention to some of the bugs I reported, as it would be nice to have them fixed.
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).
There's been a long-standing issue in Rider and also Webstorm where you try to search globally with Ctrl-Shift-F, and the search UI comes up with the searchbar unfocused and pre-filled with something random. You type what you avtually want to search for, and it either goes nowhere, or tacks onto the end of whatever garbage was pre-populated in the search bar.
This sounds like this one: https://youtrack.jetbrains.com/issue/IDEA-201301 It's a third-party issue that we, unfortunately, can't properly address on our side but there's a workaround available.
Not OP and quite satisfied with your products, but I want to take this opportunity to point at this issue for which I really would like to see some progress:
https://youtrack.jetbrains.com/issue/IDEA-256708
https://youtrack.jetbrains.com/issue/IDEA-282427 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.