[fcanela]

Major version can make someone think nvim is still unstable. My experience is the opposite.

I have being using it for 2-4 years (can't remember exactly) and got the same 0 problems I run into Vim. Earlier versions required you to recompile NeoVim to enable new features for plugins.

Yesterday I installed NeoVim in my new laptop and it was a smooth experience: Installed it using Ubuntu package manager, installed Vim-Plug for managing plugins, copied my old init.vim (or .vimrc), run vim and everything in order.

I am really happy with NeoVim. I faced no problem with it that Vim could not resolve but I know the insides being a better ecosystem for core and plugins developers, so I will stick with it.

[dmos62]

I tried jumping boat to nvim something like a year ago. One of my plugins ran into an issue, so I came back. A better question for us "old-vimers" is not "is nvim stable, because I'd like something modernized", but rather "what does nvim have that vim doesnt". I'm actually asking. My short glance led me to believe that it's got two things going for it: a) smoother interop with other "modern" tools b) cleaned up codebase.

I'm using the word "modern" in a derogatory fashion to underline that we often mistake new for good.

[placeybordeaux]

The major reason I use neovim is because with the addition of :terminal command I no longer need to remember tmux commands and with the add-on neoterm I have a one button command to send the current selection (or line) to whatever terminal I please.

This means that when developing code in any language that has a REPL I can test it out as I develop line by line.

[yamaneko]

I've been looking for something like this in vim for a while (something like Emacs + ESS). I've found a few plugins and workarounds using tmux, but nothing as smooth as you said. I'll try it out.

[thomastjeffery]

AFAIK, the main feature neovim will have is the ability to replace viml with lua wherever you want to.

According to the roadmap[1], lua will be built-in in 0.3.

[1] https://neovim.io/roadmap/

[apazzolini]

inccommand is one of the coolest features I've seen. I haven't made the switch to nvim yet, but this is high up on the reasons to do so for me.

https://www.youtube.com/watch?v=dY9dME3l-iQ

[chousuke]

I switched to neovim for faster syntax checking with Neomake. Syntastic with vim was unusably slow.

I don't know if anything has improved with vim since (probably, with 8.0), but I have no reason to go back, either.

[mcjiggerlog]

I got frustrated with how slow syntastic was too, but I have just upgraded 8.0 and have switched to using https://github.com/w0rp/ale for asynchronous linting and it's working very well.

[ramy_d]

I'm interested in neovim as well and I think you're asking a legitimate question. I would also add that if neovim is developer-friendly(er?) then that could also be a reason.

[dkersten]

Agreed. I've been using it for about 2 years without issue. I've also recently (within last 3 weeks) installed it on a fresh OS X install (on two, actually) and the experience was without incident and hassle free.

The only thing that I had issues with was plugins using the remote api from node because I kept forgetting to install node_host (which was mentioned in the README and I just overlooked). Once I remembered to install that (and node locally), everything just worked.