3 ms·
The 'ol "raising awareness" argument is way too slippery to be nailed down and often leads people to finding exactly the interpretation w/r/t utility that they
by forgottenpass 11y ago
The 'ol "raising awareness" argument is way too slippery to be nailed down and often leads people to finding exactly the interpretation w/r/t utility that they want.
Regardless, I think it's pretty reasonable to suggest that telling a community of developers "old code is a bit shit" isn't useful. Especially when the code in question is on a codebase that already has a serious modernization effort underway. And there are already numerous better presented articles online introducing the ways open source could use someone's contribution and calls the reader to action.
Sitting around and "providing criticism" ad nauseam is also a hindrance, disservice, and bikeshed.
- djur 11y agoThe author of the blog post[1] associated with that code sample has, in fact, attempted to submit patches to the original vim codebase. Many people have. They were rejected. That's why neovim exists now. So this is providing criticism in the service of providing a solution. [1]: http://geoff.greer.fm/2015/01/15/why-neovim-is-better-than-vim/ http://geoff.greer.fm/2015/01/15/why-neovim-is-better-than-v...
- mreiland 11y agoThe author is not the one who was being responded to, that's a lazy strawman argument.