Re:GitHub abandons 'master' and 'slave' terms to avoid row
by aeonsky on Monday June 15, 2020 @03:22PM
(#23531818)
Once again, the usage here has nothing to do with master-slave idea. Obviously there is precedent for breaking changes. The benefits must outweigh the costs, the cost here is monumental, and the benefit here is non-existent.
Yes, because there's no precedent for non-essential changes which break code. Maybe there's a good reason not to change the "master/slave" terminology but this sure as hell ain't it.