So an IDE is a code editor that ships with an LSP server, not just an LSP interface? (Doesn’t have to be LSP as such but “stuff that an LSP server does”).
I would say that an IDE is something that includes build/run tools integrated into it. Everything else is just a text editor. (But that’s just my opinion of course)
To expand on my point, I don’t think it makes sense to call vs code an integrated development environment if it doesn’t actually have the environment integrated.
Visual studio and idea would be examples of IDEs, they actually have all of the tools and frameworks needed to run the languages they were built for out of the box.
You can’t run node or python out of the box with just vs code for example, without their respective tooling, all vscode can do is edit the code and editing code is not functionally different from editing any other text.
So I maintain that both vim and vscode are text editors and not IDEs
So an IDE is a code editor that ships with an LSP server, not just an LSP interface? (Doesn’t have to be LSP as such but “stuff that an LSP server does”).
I would say that an IDE is something that includes build/run tools integrated into it. Everything else is just a text editor. (But that’s just my opinion of course)
To expand on my point, I don’t think it makes sense to call vs code an integrated development environment if it doesn’t actually have the environment integrated.
Visual studio and idea would be examples of IDEs, they actually have all of the tools and frameworks needed to run the languages they were built for out of the box.
You can’t run node or python out of the box with just vs code for example, without their respective tooling, all vscode can do is edit the code and editing code is not functionally different from editing any other text.
So I maintain that both vim and vscode are text editors and not IDEs
I’d say build and run tools are pretty integrated into vim. Type
:makand there you go, it’s not like vs studio would be a single process either.