Live data from Hacker News

On 2022-04-05, the default branch will be renamed from “master” to “main”

github.com

1–10 of 57 posts

Re: On 2022-04-05, the default branch will be renamed from “master” to “main”

#5
Is this strictly a western phenomenon or a United States phenomenon? I'm generally curious because I live in the US and I feel like this is very much culturally limited to the US, but I could be totally wrong.

I visited most of the world but as a tourist you don't always see deep cultural problems that may be present. I do know the US education system teaches a very United States centric view of slavery. It's literally as if they don't acknowledge that slavery was a worldwide thing and that even during the times of the primary civil rights struggle in the United States slavery of people was still an actual thing in other parts of the world.

So I have real genuine curiosity to know are we alone in the world in this hyper apologetic attitude to the point we cannot use terms like these in engineering context?

Re: On 2022-04-05, the default branch will be renamed from “master” to “main”

#6
post #2

> Why is this change necessary? In order to be as inclusive as possible, all the default branches for our GitHub Actions repositories are named main. Saving the world, one codebase at a time!

This but unironically

Re: On 2022-04-05, the default branch will be renamed from “master” to “main”

#8
There is a term for well intended, but useless attempts at inclusiveness: "buttering the cat". I think this is a prime case.

Do we have to change "master's thesis" or "golden master" or "scrum master", too? No, because that is a different word!

Now what I really did find off-putting is the use of master in "master and slave", as in IDE drives or in I2C. When I first heard it I didn't really bother me personally, but I was confused why somebody would choose such an inappropriate analogy. I would totally be ok with changing that to something more neutral.

Re: On 2022-04-05, the default branch will be renamed from “master” to “main”

#10
Isn't this solved by a large scale find-and-replace for existing scripts? Sure, the changes can be inconvenient but it's not like a major API change or something. They've also been printing out warning messages since December 29th according to the issue, so I'd expect that people would have updated their pipelines by now.
Post reply on HN