VSCode vs Neovim
A while ago I wrote about the fact that I was using Vim motions in VSCode and that I was exploring Neovim.
Since then, I have really fallen in love with Neovim (although sometimes it was more of a love-hate relationship ;-) ) and I use it full-time now. In this post I want to explain why and critically compare my experiences with both tools.
(Before we start, just a quick word about Neovim vs Vim. I guess most of my observations will hold true for regular Vim as well, although there are some things that make Neovim a superior product, such as its builtin LSP (language server protocol) client, builtin terminal emulator, and embedding of the Lua programming language.)
Installation and setup
Proponents of VSCode will say that it’s much easier to install and setup, while proponents of Neovim will say that if you want to do VSCode right and if you know what you are doing in Neovim, there is really not much difference.
When I started with Neovim I was a complete newbie (still am, really), so I would have to agree that setting up Neovim is time-consuming and comes with a learning curve. LSP might be built in, but installing the language servers or getting autoformatting and autocompletion to work was not trivial. However, now that I’ve done it, it would be really easy to (re)do a vanilla install, because…
