Comment on If "Master/Slave" terminology in computing sounds bad now, why not change it to "Dom/Sub"?
AA5B@lemmy.world 4 weeks agoTake 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
SpaceCadet@feddit.nl 4 weeks ago
Can you not please with the condescending language? Maybe you’re the one who should take a breath and read it 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 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.
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.