And thanks to recent developments in cross-editor infrastructure projects like tree-sitter and LSP, editors like VSCode, Emacs, Sublime Tex, and even public nuisances like vim can all advance at the same time and benefit from each other's development work in areas where the editors aren't differentiated.
We're very close to a world in which we don't have N implementations of finding the start of a C function or figuring out what parts of a Python buffer are keywords.
Somehow, Microsoft managed to invent LSP for VSCode and then abandon some parts of it just a couple of years later -- e.g. python language server is dead, pylance is there instead, closed source, VSCode-specific and with prohibitive license. Most language plugins in VSCode don't use LSP anymore IIRC.
While it may be true that pylance is closed source and vscode specific, pyright[1] is MIT. Pylance does appear to still be a language server as well. As far as I know, most language plugins still use LSP, including Typescript/Javascript, Rust, and Go.
Others here seem to have taken this as tongue-in-cheek. On the first read I took it as "I think vim is ridiculous". I'm honestly curious to know which it is (or if both are inaccurate).
Of course it's tongue in cheek. Vim is venerable high quality software that a lot of people love. Emacs people dunking on vim (and vice versa) is just an old traditional joke with no actual animus behind it.
I'm well aware of the decades long "feud" between emacs users and vi/vim users. But that isn't always just harmless joking around either - there are people in both camps that can be quite nasty about it.
At any rate I didn't read your comment as being "and emacs user dunking on vim" (you mentioned emacs in a list of editors, but it wasn't obvious that you were coming from the emacs camp). A lot of people scoff at vim because it works so much differently than anything else they've used before (mostly due to modal editing). I guess that was the vibe I got from my first reading of your comment, but I'll just chaulk that up to there being no "tone of voice" when reading text.
Personally I am in both camps - I use both editors. and like both of them for different reasons.
We're very close to a world in which we don't have N implementations of finding the start of a C function or figuring out what parts of a Python buffer are keywords.