I've long felt that "trunk" is a much better name than "master" or "main".
Update to Git changes the default of init.defaultBranch to main
21–30 of 271 posts
Re: Update to Git changes the default of init.defaultBranch to main
#22If I say "you are the master of your own destiny", is that offensive, because the word "master" is always offensive? I think that "main branch" sounds fine, it makes as much sense as "master branch", but I'm irked that people are always caving to word policing. Like, we're just going to scratch a whole bunch of words from the dictionary because someone somewhere is offended? The other day, people at my workplace were…
It depends on the person. Likely some people could be offended and some people wouldn't. The more relevant question is, should we care about those people's feelings. We could apply this suggested rationale to any hypothetical or actual use of language. What people find offensive tends to be deeply personal. Look at comedians who tell a joke that 'cross a line' -- some people will say it's nothing, some people will sa…
It seems to me like the people actually forcing these superficial changes through shaming and bullying are actually, for the most part, privileged upper middle class white people. That was definitely the case with the NIPS => NeurIPS conference renaming. That whole thing got started by some white dude on twitter.
Re: Update to Git changes the default of init.defaultBranch to main
#23Re: Update to Git changes the default of init.defaultBranch to main
#24This will save so many slaves.
Re: Update to Git changes the default of init.defaultBranch to main
#25What exactly is the rationale behind changing the default branch name? It seems like significant effort is being devoted to this (code changes, fixing broken CI, etc.) but I don't understand why any of it is necessary.
Re: Update to Git changes the default of init.defaultBranch to main
#26Will there be a warning if you try to use 'master' as a refname if it doesn't exist but 'main' does? I assume beginners using educational resources that aren't up to date with this change will be really confused.
Re: Update to Git changes the default of init.defaultBranch to main
#27Political issues aside, it seems that 'master' was hardcoded in several places on the code
I'd have imagined that it was more of a config issue than code, but apparently not.
Re: Update to Git changes the default of init.defaultBranch to main
#28Sigh... sad to see the tech community bullied into compliance over a non-issue by political correctness activists. It's not really that big of a deal (and in some ways "main" is better anyway because it's 2 characters shorter), it's just the principle of the thing that bothers me. I would rather see projects and people stand their ground instead of caving to pressure anytime a twitter mob comes along.
It’s sad to see so many in the tech community waste electrons by complaining over and over again about how something is such a non-issue for them that they can’t stop talking about it.
Re: Update to Git changes the default of init.defaultBranch to main
#29Given the motivation for this change -- will the same people be advocating that we must refer to main in HDDs that are in a RAID configuration? Seems a touch over-sensitive in my book. 'main' is a better choice because it's shorter -- it's also a keyword in many C based programming languages that programmers are inherently slow to write/override. They should have been the stated reasons.
I think in that context "slave/master" is much worse than just "master node", as it's explicitly that relationship. In the ATA spec for example, the master/slave terminology no longer appears:
https://en.wikipedia.org/wiki/Parallel_ATA#Master_and_slave_...
Similarly, Jenkins started moving from "slave" to "agent" in 2016, and is now working on other terms such as master, whitelist/blacklist, etc:
Re: Update to Git changes the default of init.defaultBranch to main
#30Given the motivation for this change -- will the same people be advocating that we must refer to main in HDDs that are in a RAID configuration? Seems a touch over-sensitive in my book. 'main' is a better choice because it's shorter -- it's also a keyword in many C based programming languages that programmers are inherently slow to write/override. They should have been the stated reasons.
In RAID, unlike in git, the word "slave" is also used in conjunction with "master".
That seems to inherently raise some negative associations... and it's not like "primary / secondary" aren't easily available substitutes.