[btipling]

I'd add to that to try and start using neovim. I've switched to it on Mac without a hitch and we (Floobits) have already moved our vim plugin to use the new neovim python-client plugin for much better async behavior. Making an async plugin for NeoVim is pretty trivial, here's a clock in your status bar:

https://gist.github.com/btipling/0d6faa80b24ccee5caea

Note this requires +python, :he nvim-python for how to get that (involves pip install neovim)

You can't do something like this clock in vim without the feed keys cursorhold hack that breaks using leader keys. Otherwise I'm still using vundle and have made 0 changes in my .vimrc other than move it all to .nvim and .nvimrc. All my plugins and vundle worked out of the box.

[sooheon]

I had put neovim out of mind and settled for emacs/evil, but seeing an actual use case for the new plugin system makes me hopeful for it's fast growth and adoption.

[teacup50]

Remember that floobits are the people that threw a tantrum when upstream vim wouldn't accept their patches, and have a vested ego interest in pushing a vim fork.

[tuhdo]

Imagine that one day you want to use 10 plugins and have to setup all 10 language environments to use those plugins, and you have to set the whole thing on Windows...

[Gracana]

Does vanilla neovim offer anything that a vanilla vim user might like? I imagine I will make the switch at some point, I just wonder if there's any compelling reason to do so sooner rather than later.

[btipling]

It's pretty much still the same experience. Once plugins that take advantage of the async and when gui's take advantage of the API I'm pretty sure neovim will not just be equal, but far superior.