News for hackers. Stuff that matters.
Re:Todo List for Vim by lr1970 on Tuesday January 26, 2021 @06:42AM (#25914689)
Well, The Vim's BDFL is not that benevolent after all, hence the neovim fork.
Re:Todo List for Vim by chrismorgan on Tuesday January 26, 2021 @07:17AM (#25914945)
As 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.

Re:Todo List for Vim by mxcrossb on Tuesday January 26, 2021 @07:35AM (#25915112)
I 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
Re:Todo List for Vim by bbrks on Tuesday January 26, 2021 @07:43AM (#25915171)
You 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%22GitHu...

Re:Todo List for Vim by inshadows on Tuesday January 26, 2021 @08:29AM (#25915528)
BDFL 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.