> It's easier to maintain one codebase than to maintain two forks.
Not necessarily; if the two codebases are maintained by groups of people with incompatible ideas about how the code should work and what it should do, then keeping things separate is much easier.
> If development of vim dropped and neovim was nominated as its successor, I'd think most vim users would be just fine.
Agreed; they don't diverge that much from an end-user's perspective.
Not necessarily; if the two codebases are maintained by groups of people with incompatible ideas about how the code should work and what it should do, then keeping things separate is much easier.
> If development of vim dropped and neovim was nominated as its successor, I'd think most vim users would be just fine.
Agreed; they don't diverge that much from an end-user's perspective.