re: My editor journey: sublime, vim, emacs, vscode VIEW POST

re: Pretty surprised to see this thing with the vim repo where contributors don't get to be author in the repo. Anyone knows why is that?

It's because vim has been around looooong before GitHub, and was only moved to GitHub (relatively) recently. Bram is old-school and probably just uses the project management strategies he always has. Most vim development takes place on the mailing list anyway. I'm not saying it's great how he does it, but it's not super realistic to expect a project that's been around since 1991 to fit the normal GitHub workflows.

There are other good reasons to use neovim, but this one is anachronistic, in my opinion.


Why would you want to adapt your workflow to fit one certain VCS when your project is basically driven by you as the BDFL?

code of conduct - report abuse