Hacker News new | ask | show | jobs
by gradientsrneat 718 days ago
I keep hearing of bugs and breaking changes in neovim, with no sign of it affecting the upstream vim. I am a little frustrated that neovim could give people a bad impression of vim from a stability/compatibility standpoint. Unlike emacs and atom, where you can modify the editor fundamentally, vim is extended with sandboxed scripting language(s) (I assume the same is true with neovim as well), so there's no fundamental reason why an update should break your plugins. Conflicts can occur due to overlapping hooks, but VSCode has the same problem. To be clear, I'm not suggesting people switch their text editor.

Would love to hear from a more seasoned vim user if I'm missing some egregious stumbles in vim's updates that affected their workflow.

1 comments

e.g the Lua API changes