Live data from Hacker News

GitHub is working on renaming default branch from “master”

twitter.com

161–170 of 280 posts

Re: GitHub is working on renaming default branch from “master”

#161

Earlier quoted context omitted.

You keep complaining about indulging! What's wrong with indulging in something every once in while?

If your indulging hurts others, then it is something worth complaining about.

I see no supporting argument for “replacing master with main at GitHub hurts others”; is it somewhere in this thread and I wasn’t able to see it unassisted? If not, we would benefit from you typing it up.

Re: GitHub is working on renaming default branch from “master”

#162

"main" does seem like an objectively better word to use. The definition fits better in almost every use case. May seem like a silly gesture to some, but imagine feeling an emotional trigger every time you had to use a basic tool for your job. That'd piss me off.

One big problem with "main" is it's very similar to the already well-established branch name "maint".

Re: GitHub is working on renaming default branch from “master”

#163

Earlier quoted context omitted.

If your indulging hurts others, then it is something worth complaining about.

I don't exactly understand how you're hurt by this, but fair enough. Utilitarianism is a philosophical framework. It's not for me, but based on your comments you might be into it: https://en.wikipedia.org/wiki/Utilitarianism

I am not.

Re: GitHub is working on renaming default branch from “master”

#164

Earlier quoted context omitted.

If your indulging hurts others, then it is something worth complaining about.

I see no supporting argument for “replacing master with main at GitHub hurts others”; is it somewhere in this thread and I wasn’t able to see it unassisted? If not, we would benefit from you typing it up.

go to the top of this thread chain

Re: GitHub is working on renaming default branch from “master”

#165
Personally I think this is a mistake. As we all know, English words have context, the meaning is adaptive depending on the situation. "master" branch has precedent, we have trained our brains to think about "rebasing onto master". This small change will be disruptive, forcing us to unlearn existing, common phrases. Whitelist & blacklist I support discontinuing, however master is a homonym so doesn't have the same obvious connotations.

Re: GitHub is working on renaming default branch from “master”

#166

Meanwhile slavery still exists in Libya. I don't mind renaming it but it feels like a token action without any real weight.

Chattel slavery and slave markets have existed in Mauritania since before the first Europeans even set foot in Africa, and to this day they refuse to end the practice and have told the UN directly that they refuse to end the practice every time another UN member raises a fuss about it.

So yes, this is a token action meant to appease those that are never truly appeased due to their rapid movement of goalposts.

Re: GitHub is working on renaming default branch from “master”

#167
post #152

Why is there a lot of presence of these virtue-signaling SJW types in tech?

Bougie malcontents LARPing as revolutionaries and moving from industry to industry like a swarm of locusts has been going on since at least the '90s, it's just now their ability to be noticed is greater due to advances in communications platforms.

Re: GitHub is working on renaming default branch from “master”

#168
post #139

Earlier quoted context omitted.

...because this is slacktivism lite. Rather than addressing actual issues facing african-americans today, we're engaging in silly naming changes that will have zero impact on 99.9% (optimistically) them ...because I don't want to be paying the externalities (workflow changes, having to keep up with the new "correct" naming) caused by a game of "who can be the most woke" between a vocal minority of progressives

Your first bullet is an argument against this change as being suboptimal. That there's a more optimally utilitarian use of the resources, which I get. The thing I don't get about this argument is that nothing Github (or any of us except for some weirdos) does is optimally utilitarian. They have a cartoon mascot! They don't _need_ that. You're not upset that they pay someone to draw Octocat, why be upset about this? Y…

It's a combination of the two factors. If a group of people want to one up each other by refactoring their side projects to be as woke as possible, that's fine by me. But if they're doing it and causing breakages and/or forcing everyone else to adapt, that's where I draw the line.

>A vendor changing something like this is par for the course, right? Why such an extreme reaction?

I'd be similarly pissed off if an upstream API provider suddenly decided to change all their identifier names for stylistic purposes. eg. the CTO woke up one day and decided that all of their API endpoints should be changed from camel case to snake case.

Re: GitHub is working on renaming default branch from “master”

#169

Earlier quoted context omitted.

I see no supporting argument for “replacing master with main at GitHub hurts others”; is it somewhere in this thread and I wasn’t able to see it unassisted? If not, we would benefit from you typing it up.

go to the top of this thread chain

I reviewed your initial post https://news.ycombinator.com/item?id=23500764 and I was unable to parse out of your objections why you think that this change hurts others. Could you summarize?
Post reply on HN