I think that's just the usual "not 1.0 yet". IIUC the goal of cleaning up the C-code is not yet complete nor is the "new plugin architecture" (but vim plugins work). I find it very stable and everything I previously used in vim works fine.
Their issue close rate is impressive, as well as the long list of RFCs in the pull-requests queue, a large number of which are cleaning code and tests.
pros: it's basically the same as vim.
future pro: cleaner code, more stabile/better perf, new package ecosystem.
cons: it's not vim. You can update more frequently. If you have a really old machine it won't run neovim (but will almost certainly be "supported" by vim).
You didn't cite the biggest advantages of neovim: for example, the possibility to embed neovim inside IDEs or background processes. You did mention the new plugin architecture, which is quite exciting.
Regarding the support of old machines, it doesn't matter at all, really. Even vim 1.0 would be enough for old machines. I'm not aware of anyone that wants to develop in an old machine. At most, you might need to ssh into it, and even vi is good enough :-)
Comments
I think that's just the usual "not 1.0 yet". IIUC the goal of cleaning up the C-code is not yet complete nor is the "new plugin architecture" (but vim plugins work). I find it very stable and everything I previously used in vim works fine.
Their issue close rate is impressive, as well as the long list of RFCs in the pull-requests queue, a large number of which are cleaning code and tests.
pros: it's basically the same as vim. future pro: cleaner code, more stabile/better perf, new package ecosystem. cons: it's not vim. You can update more frequently. If you have a really old machine it won't run neovim (but will almost certainly be "supported" by vim).
You didn't cite the biggest advantages of neovim: for example, the possibility to embed neovim inside IDEs or background processes. You did mention the new plugin architecture, which is quite exciting.
Regarding the support of old machines, it doesn't matter at all, really. Even vim 1.0 would be enough for old machines. I'm not aware of anyone that wants to develop in an old machine. At most, you might need to ssh into it, and even vi is good enough :-)