Why hackers moved from Neovim to VS Code
1 hacker described this switch in public comments. Their words, with links to the originals.
What hackers said about the move
“I'm personally switched from (n)vim to vscode for this reason, so I can now fiddle with a custom agent setup.”verdverm, 2026-04-09original comment ↗
Use Neovim? Get alerted when hackers criticize it.
Tell us the tools in your stack. When hackers start criticizing one of them, or moving to an alternative, you will hear about it first.
Neovim vs VS Code
| Neovim | VS Code | |
|---|---|---|
| Hackers who recommend | 10 | 8 |
| Hackers who criticize | 2 | 14 |
| Moved away from it | 3 | 15 |
| Moved to it | 10 | 6 |
Counts are distinct hackers in the sampled comments, not market share.
Criticism of Neovim
“But then instead of ctrl+z backgrounding it, I'll accidentally quit vim.”kelnos, 2026-09-27original comment ↗
“I switched from neovim because plugins and updates kept breaking it, and I never really did feel like I was in control of it anyway.”debois, 2026-03-07original comment ↗
Praise for VS Code
“I got fed up and switched back to VSCode”murlax, 2026-08-01original comment ↗
“I switched from vim to VSCode due to this feature”renox, 2026-05-12original comment ↗
“using vscodium instead of vscode is again justified.”RandyOrion, 2026-05-03original comment ↗
“I switched from Sublime Text to VS Code, and didn't care one bit how open or close either was.”dist-epoch, 2026-04-02original comment ↗
“WASM debugging in VSCode feels just like native debugging”flohofwoe, 2026-03-09original comment ↗
Other moves from Neovim
- Neovim → Emacs (1)
- Neovim → Helix (1)