3 ms·
I will agree once neovim ships on the major platforms and has functions on par with vim. Their next milestone for Windows support has continued to slip. It's be
by shortlived 10y ago
I will agree once neovim ships on the major platforms and has functions on par with vim. Their next milestone for Windows support has continued to slip. It's been at 75% complete for many months. Meanwhile, gVim is running great on numerous platforms.
It's not a knock against neovim, but I just hope they can keep things going.
- jjawssd 10y agoIs it possible that Windows users are not as interested in vim as *NIX users for historical reasons, and therefore don't care as much about support?
- fatbird 10y agoWhere it works, it's a drop-in replacement for VIM, notwithstanding differences in async implementations now.
- milesrout 10y agoIt's certainly not a drop-in replacement for vim. It doesn't support many features released in vim 8.
- fatbird 10y agoUntil vim 8, it was a drop-in replacement, retaining full compatibility with vimrc and all plugins. My switch was seamless, and that was a big goal of theirs. Vim 8 introduced features already found in neovim in an incompatible way, and now the real fork begins.
- milesrout 10y agoWell it isn't a drop-in replacement now. And it wasn't a drop-in replacement before either, on the platforms they needlessly removed compatibility with. Vim introduced features that had been being worked on since before NeoVim, in a way that actually made sense in the context of Vim, and which fit into Vim nicely.