Neovim already fragmented the community. Bram seems to have stepped up to the challenge bigtime since neovim announcement, as judged by his github activity graph.
That being said I hope they pull an io.js and merge taking the best of both vim and neovim, whatever that may be.
Something challenges you, your reaction is to ignore/quit or step up and respond.
Maybe you want to move on just for the sake of moving on? To a new generation? Can you explain why? Seems to me that the person who knows the code base 200%, who wrote/vetted the entire codebase, is better placed to add features, than newbie refactorers who didn't?
And all of that while maintaining such good backwards compatibility that almost all vim plugins work unmodified. Plugin authors only need to lift a finger to take advantage of new capabilities like async.
I didn't switch just for the sake of moving on. I switched because by any appreciable aspect, neovim and the developers behind it are simply better than vim.
They're served decently enough by older versions and I doubt that any machine running those has the resources for features provided by newer Vim versions. Even if they do, the OS support for these features might not be good enough.
Omitted in this version are:
The 16-bit DOS, OS/2 and Amiga versions, these are obsolete.
The 32-bit console version for MS-DOS/Windows 95/98
The 16 bit MS-Windows version