Editors like Vim, Emacs or VSCode are all about the plugins
I use emacs for org mode And VSCode for everything else, because simply most proramming languages have their main plugins on VSCode
The only way you can move from VSCode to neovim is, if you dont care about the plugins
Why would you VSCode if not for the plugins
They've done it before and they'll do it again.
LSP for MS and VS Code is "come, make our proprietary editor more valuable by supporting languages we can't be arsed to worry about!"
https://github.com/microsoft/pylance-release/issues/4
(I am an enthusiastic advocate for LSP otherwise.)
Truly a valid concern.
IMO TypeScript is VSCode strongest use case - I would use VS code over VisualStudio for example on C# projects when I had to edit fronted parts - it was so much better. IntelliJ TS stuff is the only thing that comes close/is on par maybe and I'm a happy camper in that ecosystem for the last few years.
None of the LSP plugins I've tried with neovim worked nearly as well as they do in VSCode (the few times I tried to spin it up for old times sake).
Can you link me to how to configure that? I have been using LanguageClient-neovim, which is a Rust plugin.
The best place to start is here: https://github.com/neovim/nvim-lspconfig
I use it in combination with nvim-compe: https://github.com/hrsh7th/nvim-compe
but comments above are suggesting that because of LSP (Language server protocols) plugins can be portable now, from one editor to another
i thought each editor needed its own plugin, and VS Code always seem to have the main plugin, didnt really come across plugins that run across multiple editor, but then i was not really checking this, next time i will check it