It sounds way less offensive to those who decry the original terminology’s problematic roots but still keeps its meaning intact.
Sure, so if there’s no need for any certain terminology outside of an agreed upon definition what does it matter if it’s called master or main or unicorn farts? Why care about Master at all?
Why care about Master at all?
I’ve already explained all my reasons, but I’ll reiterate. To summarize I basically have five main issues with it
-
The change was done in response to attempts at language policing and bullying by a vocal and militant minority. Giving into it is a form of appeasement towards an unreasonable demand.
-
The change retroactively modifies a terminology that was already agreed upon. Like, if git sprung into existence today, not many people would have an issue with it if they would call it main or trunk or primary from the get go. But that’s not what happened. Git was released in 2005 and it used master terminology. As a consequence, many existing repositories also use master. Now when someone is working with branches, like doing merges or pull requests, they suddenly have to remember: oh in this repository it is main, but in that repository it is still master. Or they have go out of their way to modify decade old repositories, potentially breaking all kinds of behind the scenes CICD stuff. Or they have to go out of their way to revert the default on all systems that they’re working on back to master. In any case, this change is a source of errors and wasted effort for zero net good.
-
It does no good in the real world other than making do-gooders feel good about themselves, and giving a capitalist entity some PR to appear more progressive than they are. We all still have masters, existing slaves are not freed, no historical wrongs of slavery or inequality are righted.
-
It’s a misguided change in this case because the word master in this context doesn’t even have a relationship to slavery. Just like a master degree you may hold, or a master key or a master recording of your favorite album have no bearing on slavery. Note that there are no “slave” branches in git.
-
Finally, in the case of git, master is simply more accurate than main because it carries a nuance (derivativeness) that main does not.
Take a breath dude. While I also don’t see how there is a connection to anything negative and think that older term was slightly more accurate, does it really matter?
If there’s any chance it helps maintain a hostile workplace/industry, it’s trivial to change. Might as well.
My company didn’t force a change but our git software changed their default:
- some repos use “master”, some use “main” and it really doesn’t matter
- the name of the main branch is based on age: before vs after the git software changed. Clearly the most important factor is people are lazy and the default is good enough
Take a breath dude
Can you not please with the condescending language? Maybe you’re the one who should take a breath and read my post calmly. Anyway, the guy above me asked, I gave an answer to cover all the bases.
The default branch name of git isn’t that important to me either, I’ll manage with main or master. But at the same time it does irk me especially since this kind of language policing has become an industry wide trend, and it’s just a stupid thing done for stupid reasons. Am I still allowed to express why I find it stupid?
it’s trivial to change
It isn’t as trivial as you make it out. I’ve already encountered repos where there was both a main and a master branch, both with different commits, because some developer got confused, and it was a nice mess to untangle. But hey, let’s change some more stuff around for no good reason.
If there’s any chance it helps maintain a hostile workplace/industry
I can think of a lot of things that contribute to a hostile workplace, but the default branch name of git? Seriously? Even the people who pushed for this don’t actually believe that themselves.
