Bram Moolenaar Discusses Developing Vim, How He Uses It, and Version 8

Re:Bram Moolenaar Discusses Developing Vim, How He Uses It, ... by libria on Thursday December 22, 2016 @07:23AM (#13236756)

Neovim's popularity is more with extension developers. My understanding is that it enables them to develop features rivaling those in IDEs. Vim users won't switch for Neovim itself, but they might if extension writers only target Neovim.

I think Neovim also has a pluggable engine, so IDE vim emulators can simply include that portion rather than implementing the functionality per platform.

[ Parent | on HN ]

Re:Bram Moolenaar Discusses Developing Vim, How He Uses It, ... by tomku on Thursday December 22, 2016 @10:20AM (#13237769)

This was true for a while, but vim 8 (and some of the last patches of vim 7) added async tasks, channels and built-in JSON encoding/decoding. It's a hassle to have to support two different interfaces, but I suspect most plugin authors are going to do that rather than force their users to use neovim. Some plugins (like neomake) already support both.

Edit: Forgot to mention, many of the improvements in vim 8 were clearly in reaction to Neovim's innovations. Both projects benefit from the other, this isn't a fight to the death.

[ Parent | on HN ]

Re:Bram Moolenaar Discusses Developing Vim, How He Uses It, ... by criddell on Thursday December 22, 2016 @09:10AM (#13237310)

Can you name a couple of extensions that somebody considering Neovim should look at?

[ Parent | on HN ]

Re:Bram Moolenaar Discusses Developing Vim, How He Uses It, ... by fmoralesc on Thursday December 22, 2016 @09:28AM (#13237409)

neomake (async execution of tasks like compiling, linting and syntax checking) and deoplete (for async autocompletion).

[ Parent | on HN ]