NeovimvsVS Code

Neovim

• Why is Neovim so hard to learn?(8/10)
• Lua adds another language to learn(5/10)

VS Code

No signals

Neovim

• Extensive configuration required before coding(8/10)
• Distro confusion - LazyVim, NvChad, AstroNvim(5/10)
• Configuration becomes maintenance burden(6/10)

VS Code

No signals

Neovim

• Why does my Neovim config keep breaking?(7/10)
• Neovim LSP breaks after upgrading (lspconfig deprecated)(8/10)
• nvim-treesitter rewrite breaks highlighting configs(7/10)
• Neovim 0.12 upgrade breaks older plugins and configs(6/10)

VS Code

• Extension conflicts and breakage(6/10)

Neovim

• Keybinding overload paralyzes beginners(6/10)
• Neovim is not a pick-up-and-code editor(7/10)

VS Code

• Limited refactoring compared to JetBrains IDEs(6/10)
• No local change history built-in(5/10)
• Git integration inferior to JetBrains(5/10)
• Requires extension hunting for basic features(5/10)

Neovim

• Plugin documentation is thin and scattered(5/10)

VS Code

• Closed-source extensions hard to debug(5/10)

Neovim

• Large codebase performance struggles(6/10)

VS Code

• High memory usage and lag with extensions(7/10)
• Struggles with large monorepo projects(7/10)
• Slow search on large projects(5/10)

Neovim

• Debugger setup is complex(6/10)

VS Code

• Electron-based means inherent overhead(4/10)

Neovim

No signals

VS Code

• Telemetry sends data to Microsoft by default(6/10)
• Not truly open source in distributed form(4/10)