Choosing Vim over VSCode
alexsci.com
alexsci.com
"This extension uses a fully embedded Neovim instance, no more half-complete Vim emulation!"
This article seems to compare an out-of-the-box vscode with a tailor made vim.config. I guarantee if he spent as much time configuring vscode as he did configuring vim he could establish equivalent environments. That vscode-neovim plugin alone (not vscode-vim) is likely sufficient.
Yes. I don't see the point, though. If I can run full neovim inside VSCode what does VSCode add?
> I guarantee if he spent as much time configuring vscode as he did configuring vim he could establish equivalent environments.
Yes, almost. For example you can make VSCode run terminals in tabs like the editor windows. VSCode supports a lot of customizing. But it still runs on Electron with a rather heavy node process on the other end -- a lot heavier than vim or neovim.
I used VSCode for over six months but ended up going back to vim. Nothing specifically wrong with VSCode, I recommend it to people who don't know how to use vim/neovim, or don't want to use those tools. But for those of us who know how to use vim/neovim VSCode feels slow and bloated with features I don't want. Personally I prefer not to use Microsoft products when I can help it, but now with VSCode (and GitHub) increasingly pushy about AI that I don't want I can do without VSCode.
half my edits still started out as ‘xterm -e vi $1 &’