[cyberax]

> On the other hand, they are notoriously slow to develop their IDEs.

I found that IntelliJ IDEs for me are almost at the perfection level. I don't really need any new changes, except for simple incremental ones like supporting new languages.

I've been using IntelliJ since 2003, and it's amazing how little my main workflows have changed since then.

[raincole]

My worst nightmare is JetBrains gets IPO (or acquired by a public traded corp).

[pulse7]

Which may happen when the founders decide to retire...

[boxed]

They do break stuff they used to have and then it doesn't get fixed for years.

For example this https://youtrack.jetbrains.com/issue/PY-39449/Deleting-param... has been broken for 4 years.

[windock]

And every release they break my Split-view workflow. It is just random thing, every time something different. The latest thing - when the current file is split vertically, new split has viewport moved to something like 20 lines below. And yes, every time it takes years to actually fix those.

[maccard]

All software has bugs. THis is no different to emacs [0] or vscode [1]

[0] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=2940 [1] https://github.com/microsoft/vscode/issues/30874

[boxed]

The problem is that they create features, and then those features BREAK later. Then in some cases they fix them and then they break AGAIN later.

They seem to be pretty bad at writing regression tests.

[lenkite]

Its looks like Jetbrains is migrating to an N IDE's for N languages approach - bloat up memory and disk so they can be paid more.

No point in buying Intellij Ultimate and installing language plugins. As is clear from this post, the language plugins will no longer see new features.

Now you need to purchase and start the IDE's for Rust, Go, C++, Python, etc. So if you are working in multiple language projects, you need $$$ purchase power. And then 64 GB RAM and several terabytes of hard disk space.

What a mess.

[highwaylights]

This is my biggest problem with the JetBrains world. It should be one IDEA and a bunch of plugins (of which Java should be one). I don't know why I need X copies of the same tool with different config files.

[wink]

Waiting 5-10 minutes for a moderately sized project to be indexed until you can do anything useful is perfection? Ouch :P

[pjerem]

Those IDEs are clearly made for big projects you work on for months/years.

Indexing is far less than 5 mins (more 1 min for a big project) and is cached. It only happens the first time you load a project.

Maybe you are of bad faith on this one.

[wink]

Mine indexes every time I boot it up, per project, so sometimes several times per week, fortunately not every day.

No, no bad faith, it's simply my number one pain point.

Imagine there are people who work on different repos/projects. Just quickly opening another up during a call? Maybe wait 5 minutes. This is decent hardware on an SSD. We're not talking about 10 year old 2m LOC mammoths, but also not "I expect it to start up in 3s like an editor and not an IDE".

[martypitt]

I suffered that exact same issue for a very long time with IntelliJ.

If you haven't tried upgrading yet, I'd recommend it. They did a huge amount of work to address the issue, and from my experience, it's significantly better in 2023.2.