JetBrains IDEs Are a Language Server With a GUI
The index is the product. Inspections, rename, debugger — then a window around them.
[ essay ]
JetBrains IDEs are a language server with a window around it: an index of your code, inspections, refactorings, a debugger, a GUI that makes “find usages” a click. The IntelliJ platform did semantic indexing long before Microsoft published LSP. LSP is the later, editor-agnostic protocol. JetBrains still ships the thicker thing: a semantic engine plus chrome.1 I do not daily-drive IntelliJ for mystic-bytes. Cursor is the editor. I have used JetBrains products as a user on other codebases. I have never been a JetBrains engineer.
The product is the index. You wait for it. Then rename is safer, the bulb is a warning, the gutter is coverage. VS Code plus a language server approximates a slice of that. The JetBrains bet is that the GUI and the engine should be one company. That is why RubyMine knows Rails, why IDEA knows Spring, why people tolerate the RAM bill. A protocol cannot love a framework that hard.
Use a JetBrains IDE when the language’s real tooling lives there and you will pay for the index. Do not open it to write Jekyll frontmatter. I already have an editor with a model in the loop. The language server with a GUI is a different default, for a different kind of repo.
— JV · Dark Heart Labs.
References
-
JetBrains Docs, “Language Server Protocol,” https://www.jetbrains.com/help/idea/language-server-protocol.html. LSP as an add-on to an IDE that already indexed, inspected, and refactored in-process. ↩