[swatcoder]

Vertical integration with the toolchain, for one. Most text editor extensions rely on least common denominator integration with tooling through an adapter layer like LSP.

And that works pretty darn well, but struggles to integrate all of the toolchain's development opportunities into the workspace environment.

Horizontal integration across workspace modules would help too. Most text editor extensions rely on a least common denominator UX language through command palettes and button arrays and human-editable config files.

And that also works pretty darn well, but struggles to integrate all of the workspace environment's features into coordinated development workflows.

There is no slight being made against VS Code to say that it's not the same as a more fully integrated development environment. It's a very powerful tool in itself, capable of meeting most developer's needs and is far more extensible and adaptable than IDE's aim for.

[OrderlyTiamat]

LSP was literally developed for vs code. Using it as an example of what text editors use to approach ide's is in the context of that fact rather odd in my opinion.