regardless of that, it’s never inconvenienced me and it’s still a net gain in readability, since main actually means what it means. have my shell scripts set up to use either one for any repo I’m in automatically.
Honestly it’s not even about convenience. As far as breaking conventions go, this one has none-to-minimal impact – existing master branches won’t suddenly become invalid. But it’s yet another instance of a subset of a subset of a subset of users getting to enforce their sensibilities for superficial reasons, and ultimately with zero effect regarding the cause they claim to represent; cultural and linguistic differences be damned.
I’d love to be more specific, but I don’t want the comments to turn into a warzone.
Claiming that master on github stems from master recordings is not only disingenuous but also incorrect.
As a FOSS alternative to BitKeeper, Git naturally reimplemented it’s naming conventions as well - and because of the power of version control - we can actually check what the original meaning was derived from:
And yes I agree that GitHub just changing the name of the default branch while keeping their ICE contracts is performative as fuck - which imo means we should both boycott GitHub and use naming conventions that don’t have a history related to one of the worst atrocities the global north has brought upon the world…
regardless of that, it’s never inconvenienced me and it’s still a net gain in readability, since
mainactually means what it means. have my shell scripts set up to use either one for any repo I’m in automatically.Honestly it’s not even about convenience. As far as breaking conventions go, this one has none-to-minimal impact – existing
masterbranches won’t suddenly become invalid. But it’s yet another instance of a subset of a subset of a subset of users getting to enforce their sensibilities for superficial reasons, and ultimately with zero effect regarding the cause they claim to represent; cultural and linguistic differences be damned.I’d love to be more specific, but I don’t want the comments to turn into a warzone.
And don’t pretend like master doesn’t mean what it means.
And don’t pretend like master doesn’t mean what it means.
Claiming that
masteron github stems from master recordings is not only disingenuous but also incorrect.As a FOSS alternative to BitKeeper, Git naturally reimplemented it’s naming conventions as well - and because of the power of version control - we can actually check what the original meaning was derived from:
And yes I agree that GitHub just changing the name of the default branch while keeping their ICE contracts is performative as fuck - which imo means we should both boycott GitHub and use naming conventions that don’t have a history related to one of the worst atrocities the global north has brought upon the world…