Neovim was started by a guy called tarruda who (if I recall correctly), after trying several times to introduce background processes to vim, was rejected, so he decided to fork vim and try to work on that alone (he wrote a post here in HN which helped neovim take off).
The main advantages of neovim are the possibility to embed it into an IDE (basically be able to use vim inside any IDE without having to create a plugin emulating it), the ability to extend vim in any language, a cleaner code base, background processes (running grep locks vim), and a few other things.
It has some good momentum. There are some contributions and definitely a lot of discussion. It has also removed a lot of cruft from the code base. It's way cleaner (with the downside of only supporting Windows/Mac/Linux/BSD, but it's a great trade) and I guess it will help to incrase community contributions, because people tend to dislike mailing lists, especially those that do not have much experience contributing to open source software.
Comments
Neovim was started by a guy called tarruda who (if I recall correctly), after trying several times to introduce background processes to vim, was rejected, so he decided to fork vim and try to work on that alone (he wrote a post here in HN which helped neovim take off).
The main advantages of neovim are the possibility to embed it into an IDE (basically be able to use vim inside any IDE without having to create a plugin emulating it), the ability to extend vim in any language, a cleaner code base, background processes (running grep locks vim), and a few other things.
It has some good momentum. There are some contributions and definitely a lot of discussion. It has also removed a lot of cruft from the code base. It's way cleaner (with the downside of only supporting Windows/Mac/Linux/BSD, but it's a great trade) and I guess it will help to incrase community contributions, because people tend to dislike mailing lists, especially those that do not have much experience contributing to open source software.