6 ms·
It's interesting that the increase in Vim commits is concurrent with the fist release of NeoVim. They've certainly both been good for each other and I'm hoping
by hrokr 3y ago
It's interesting that the increase in Vim commits is concurrent with the fist release of NeoVim. They've certainly both been good for each other and I'm hoping this won't change with Bram's passing.
- turndown 3y agoForking is usually good for the community around a piece of software but I struggle to find who made this argument originally
- kaba0 3y agoI think it is only good when the software has slowed down development. Otherwise it just needlessly splits the community.
- goku12 3y agoSpecifically in the case of vim, Bram took decisions that forced the community to choose one or the other. Like the implementation of async and the choice of a second extension language.
- The_Colonel 3y agoVim was mostly a one man show. I doubt it will be meaningully developed apart from bugfixes and such.
- arp242 3y ago> Vim was mostly a one man show. No, it wasn't, and hasn't been since the 90s (most of the gvim code was written by others back in the day, to give an example of a large body of code not written by Bram). There have been many people contributing, and some of them for years. Yes, Bram was the BFDL and the only one committing patches, but don't confuse that with "one man show".
- The_Colonel 3y agoThere were of courses patches by other people, but most big features were driven by him. Do you have some example of a big feature more recent than 20 years old gvim?
- deleted 3y ago[deleted]
- arp242 3y agoMost of the multibyte from the last few years for example. Bram didn't really record these things very well until quite recently (and even then, rather inconsistently) by just listing the author in the commit message rather than the git author field, so there's no easy way to check.