> What should be the deciding factor is the resource consumption, then: if you end up with a less refined and less capable LSP+Extension enhanced text editor, it better be lightweight, right? Well, here again it's pretty clear that those LSPs and Extensions are everything but that, and not only JetBrains IDEs start fast (which was a big area of focus recently), they also respond better using comparable resources.
What kind of nonsense is that, lmao. JetBrains IDEs absolutely choke on our Java monorepo out of the box and you have to rely on huge hacks to make it work. While VScode works just fine and stays responsive while indexing in background allowing to move around and modify files without any lag.
And GOD FORBID you close it, open it again and be greeted with 30 minutes of “indexing”.
Their tooling is so great, that they had to migrate their homebrew Java tooling in CLion to clangd (C++ LSP) based indexer.
Android Studio is another level of awful and if someone would release Kotlin LSP I’d migrate in an instant. But of course JetBrains won’t release it, because it doesn’t drive IDE sales.
I mean, immense corporate codebases is the bread and butter of IntelliJ Idea and where it has a reputation to shine. I don't doubt that you are commenting in good faith, but the exact opposite of your experience is what most people have been saying about it over the years. Have you considered reporting the issue to them?
My experience of vscode LSPs across several languages is that they too use many GBs of RAM over time, just what you would expect from an IDE (and not from a text editor), while delivering pretty poorly feature-wise (unlike idea-based editors, I can't trust vscode to know how to rename variables across languages e.g. from models into templates/SQL, and that's a pretty essential bar to cross in my book).
What kind of nonsense is that, lmao. JetBrains IDEs absolutely choke on our Java monorepo out of the box and you have to rely on huge hacks to make it work. While VScode works just fine and stays responsive while indexing in background allowing to move around and modify files without any lag.
And GOD FORBID you close it, open it again and be greeted with 30 minutes of “indexing”. Their tooling is so great, that they had to migrate their homebrew Java tooling in CLion to clangd (C++ LSP) based indexer.
Android Studio is another level of awful and if someone would release Kotlin LSP I’d migrate in an instant. But of course JetBrains won’t release it, because it doesn’t drive IDE sales.