24 ms·
Pretty much agree with all that. There are two places where I do fight against it is where someone references external established standards/documents. For exam
by viraptor 6y ago
Pretty much agree with all that. There are two places where I do fight against it is where someone references external established standards/documents. For example if you're using SPI, the devices are master and slave. Until SPIv2 changes the naming, software using it should match it. Same for changing public API without leaving backwards compatibility names.
The second one is if the name is already massively spread and a known brand which just can't be "renamed". Like in Rubocop case - you can't rewrite every mention on the internet. If you're going to kill the brand... it's just not worth it.
Otherwise, either do a quick change, or ask "if you care enough, please submit a PR" and just be done with it.
- scrollaway 6y agoWhat's the Rubocop case?
- viraptor 6y agohttps://github.com/rubocop-hq/rubocop/issues/8091 https://github.com/rubocop-hq/rubocop/issues/8091 Proposal for removing "cop". TL;DR: Rejected by author because the name is so established as a brand it would take massive effort to change.
- mercer 6y agoYeah, that one seems reasonable to me too. I am somewhat cop-averse (at least in the US), but the justification for keeping the name are reasonable.