Hacker News Reader

Comment by giancarlostoro | Hacker News Reader

Neovim is a different beast than vi or vim, definitely suggest looking into it. It's insanely capable, and if major IDE's invested time into supporting it, you wouldn't need to ever choose between Neovim or an IDE, you could just use both together. I think currently VS Code is the only editor that supports Neovim properly, there might be others though.

The neat benefit is you get all the editors own plugins + all of Neovims plugins.

View on HN

If stuck with classical UNIX editors, I rather spend my time on Emacs.

I know VI well enough to save me when nothing else is available, specially helpful when dealing with servers without root account access, and noexec $HOME, and that is good enough for me.

If Emacs ever does the headless UI thing I will crawl back to it, in all honesty. I like the idea of consistent editor key bindings across editors and consistently being able to reuse a powerful editor with any IDE.

What does it mean for an IDE to support neovim?

it probably means to run actual instance of neovim and use it as a backend for current editor's content.

Except you get features of both editors, so IntelliJ would still have their auto complete intellisense features, and Neovim key bindings would still work, and Neovim plugins as well.

Neovide is much better editor that natively supports neovim than vscode. All vim plugins in vscode have conflicts with other extension rendering them useless

Reply on news.ycombinator.com