Earlier quoted context omitted.
> I don't understand this point, and I tried to parse it and still don't. (...) If vim maintainers don't want neovim to exist, they should have accepted the merges earlier. If they disagree with the merges (which I think they did), then that power doesn't belong in Vim anyways It's a very simple point to understand: whether the merges are good or not, the presence of a fork still "splits the Vim community and takes p…
> That's regardless of people "having the right to fork". Yes they do. But also yes, if they exercize that right, they do split a community and divert interest from a project to 2 projects. You're not dividing the same-sized pie. The alternative to a fork is a single project with fewer contributors. The alternative to two communities is a single community that's not as large as the two would've been, with a good chun…
We do. Neither vim-or-vim-fork editor users nor vim-or-vim-fork-potential-devs are going to see any significant jump in population from the presense of neovim. People who are new to vim-style-editors and go to neovim are mainly people who would have gone to vim if neovim didn't exist.
And from people contributing to vim via themes, plugins, etc., some have taken their talents to neovim, which would have stayed with vim if neovim didn't exist.
>Forks are good
Well, the prevalent wisdom of 30+ years of FOSS has been that they're mostly bad.