Comment by pjmlp
2 days ago
Including everyone that ships Chrome with their application as "native" app.
VSCode gets a pass, because apparently it is the only programmer's editor that many only care about providing plugins nowadays.
2 days ago
Including everyone that ships Chrome with their application as "native" app.
VSCode gets a pass, because apparently it is the only programmer's editor that many only care about providing plugins nowadays.
The ubiquity of their plugin model is why. Near all editors have a VS code plugin compatible layer
Yeah, and with it Eclipse wins a second time, especially on embedded where Eclipse CDT forks were replaced by VSCode forks.
"Project Ticino: Microsoft's Erich Gamma on Visual Studio Code past, present, and future"
https://www.theregister.com/2021/01/28/erich_gamma_on_vs_cod...
> Near all editors have a VS code plugin compatible layer
Huh, never heard about this before, and took a look at emacs and vim/neovim as those are the two most popular editors I know of, neither can run VS code plugins, that'd be crazy if true.
If you count LSP (Language Server Protocol) as a VSCode plugin-compatible layer as LSP was built and standardized by the VSCode team (so many do), then Emacs and Neovim are full of VSCode-compatible plugins today. One of Neovim's selling points right now over bare Vim is better/more direct LSP support.
2 replies →
Very long time vim/neovim user here. I can't remember names atm and can't check, but I have definitely seen plugins that run a headless or subset of VScode in the background to pull info from it. It may not be super common, but it is being done
1 reply →