4 ms·
Well, The Vim's BDFL is not that benevolent after all, hence the neovim fork.
by lr1970 6y ago
Well, The Vim's BDFL is not that benevolent after all, hence the neovim fork.
- chrismorgan 6y agoAs one who depends implicitly on Vim, he seems to me very benevolent: he doesn’t let other people break Vim. I greatly appreciate Vim’s stability. But it’s also not only Bram that can develop it, especially on maintenance patches (as distinct from new features). I can’t think of any particular times anything regressed in Vim, except that I have a feeling there was one. A few times over the years I’ve found bugs, and each time, I’ve either submitted a patch which has been rapidly accepted, or reported the bug and it’s been fixed rapidly by Bram or someone else.
- mxcrossb 6y agoI just checked the GitHub project for neovim and see that their CI is failing. That maybe is a good symbol of the differences in priorities
- bbrks 6y agoYou might want to check the CI history of vim too if you want to compare meaningless metrics. https://github.com/vim/vim/actions?query=workflow%3A%22GitHub+CI%22+branch%3Amaster https://github.com/vim/vim/actions?query=workflow%3A%22GitHu...
- inshadows 6y agoBDFL is not about taking any code that people throw at you. Look at LKML at how many iteration patches go through before they are merged.