Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This would save so much time wasting. When someone says "Can you push that to the master branch" there is nothing that ties that statement to slavery or racism so there is nothing wrong with it.


The best thing to do is to ignore these people, they will never be happy so there's no point trying to please them.

If you ignore someone who is never happy then in time they may respect you, but if you always comply then they will never respect you and their perceived power over you simply increases, which means they feel empowered to ask for more and more.


But how will tech Cos show they're woke if they can't just change the names of things and say they did something important?

It's literally a bragging point at my new Co.


Anyone else intentionally making master branches in new repos at work?

It's hilarious watching the amount of mental energy people waste on this.


> ignore these people

Unfortunately for the rest of us, they've been put in charge.


I'd say they took charge, weaponizing empathy and recruiting useful idiots and powerful cowards.


Exactly


> there is nothing that ties that statement to slavery

I would say there is. That's where the language comes from. BUT I do not think that necessarily means that this is a callback or reference to enslaved _people_. Master/slave model accurately describes the model in a way that people can hear the terminology and understand what is happening without knowing details. It doesn't condone/promote slavery, it doesn't have anything to do with enslaving people, and in no way does it even encourage such behavior.

Context matters, a lot. And to be honest I didn't hear anyone complaining about this (and I live in an extremely liberal place), so it came off (to me) as a grab for social currency (_especially_ since GitHub didn't use the term "slave". GitHub was using "master" in the sense of "main" or "principle" and so I didn't get even understand). If you try hard enough you can make anything reference race, but at the end of the day what really matters is context and how people perceive things. If no one (or realistically few people, because there are people looking to make issues) are making these connections AND no one is being harmed, then we shouldn't really be worried about it.

Edit: wanted to make clearer that I'm talking about two different terms of the usage "master". One from master/slave model[0] and one that GitHub uses (which uses the adjective version of the word which means "main" or "principle"). And that the GitHub version does not reference the former version. I know we're talking contentious subjects here but I'm trying my best to convey what is in my head. I'm open to new opinions but bear with me. Language is complicated.

[0] https://en.wikipedia.org/wiki/Master/slave_(technology)


> Master/slave model accurately describes the model in a way that people can hear the terminology and understand what is happening without knowing details.

Except it has absolutely nothing to do with slavery at all. The master branch is akin to the master record, that holds the true and complete copy. A master branch evokes mastery of a subject, like a Masters degree.

Except now, everyone just submits to the idea that the word master only has context in master/slave terminology.


Yeah so there is a master/slave model but I agree that that's not what GitHub was using. I tried to clarify this with my parenthetical statement but apparently did not do so sufficiently. Any suggestions of how to edit?

> A master branch evokes mastery of a subject, like a Masters degree.

I would actually say that that a Master degree is using a different definition (though both part of the adjective usage). For a master branch (or master document, master copy) I'd say it is the definition that is "main" or "principal". Whereas a Masters degree is having mastery over something, which is akin to high proficiency.


Master/slave model has nothing to do with git's master which is "master copy" like as in record mastering. What you say is valid for SCSI or whate et though.


Sorry I was trying to convey that. But language is often messy. I completely agree with you. I thought my parenthetical mention of Github clarified this but I guess I wasn't clear. I'm not sure how to edit to resolve. Any suggestions?


You're wrong - etymology is via bitkeeper which has slave repositories and master repos.


https://mail.gnome.org/archives/desktop-devel-list/2020-June... for a description of what happened; tldr it isn't.


That link doesn't say anything contrary to what I said, and indeed includes a link to a twitter thread saying that Bitkeeper may very well be the origin of the 'master' terminology in git.


> how people perceive things.

ah, but which people? the most reasonable and intelligent people? the traumatized and most sensitive people? The former I'd say yet, the latter I'd say go get some therapy and keep your trauma to yourself, it shouldn't drive the larger discussion.


> Language is complicated.

Sure, it's organic, but there's no god-of-the-gaps in there. It is knowable. A language isn't as complex as a human brain. Nor is it living, it can be decomposed at will.

Linguists have been working like gang busters to iron it all out. Steven Pinker, Noam Chomsky, et al...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: