GitHub renaming default branch to “main”
twitter.com
twitter.com
https://news.ycombinator.com/item?id=23500093 (138 points/224 comments)
https://news.ycombinator.com/item?id=23518123 (127 points/206 comments)
https://news.ycombinator.com/item?id=23519813 (44 points/84 comments)
https://news.ycombinator.com/item?id=23522859 (15 points/5 comments)
I guess I better get rid of my Master’s degree before some people think I’m a slave owner.
We're not against anti-racism, we're anti-nonsense and this is just about as nonsensical as it gets. Actual effort to solve the very real problems that the US faces with regard to race would involve donations of money and staff time to help out minorities, enough to cause some level of financial stinging. If these organizations did that, that would be actually worthy of praise.
[1] sorry, blockmailing
See https://github.com/bitkeeper-scm/bitkeeper/blob/master/doc/H... for master/slave terminology.
In any case, the git dev responsible for the choice has made their views known: https://twitter.com/xpasky/status/1271477451756056577
> "master" as in e.g. "master recording". Perhaps you could say the original, but viewed from the production process perspective.
> A clueless Central European youngster whose command of English was mostly illusory came up with the term, which is why it isn't very obvious...
https://twitter.com/xpasky/status/1272280760280637441?s=20
I always thought it meant "master copy"...
Digging into the usage of Master for "Master Copy" you could say the intention is that the master copy has authority, or highest standing, over all other copies, so more or less the meaning they were trying to avoid.
They are not unrelated. I'm not making an argument whether the word is inappropriate or not. Just pointing out an etymological fact.
Apparently, nobody here understands that.
There are multiple definitions of 'master'. This has no connotation with master and slave. My other branches are not someone inferior to the master branch, and the master branch does not command the other branches. The other branches are normally an improvement on master, and master is usually transformed to resemble another branch.
If you want to fight systematic racism in society, changing the word master, when master has nothing to do with master/slave, seems a nice gesture, but rather kneejerk, and forces people to do a lot more work, all because someone failed to use a dictionary, which causes annoyance rather than a change of mindset.
Maybe elephants will be offended by this name? Who knows.
If he wants to change it from master to main/upstream I'm on board. shrug
If something this ... inconsequential to me can make some folks more comfortable I don't care. Think of it this way, it saves 2 bytes! Course upstream then takes those bytes from origin. So it is a wash after all.
What bothers me a lot, that a group of people basically decide for the whole world, cultures and countries how should they feel about things. This clearly was a case with Rubocop renaming, where bunch of developers aggressively attacked Bulgarian maintainer [0] to rename Rubocop library because of the `cop` part. They obviously didn't care, that in many other countries police is actually protecting people and is being respected. And argument of "(in US) the word "cop" has an uncomfortable feeling about it" was enough to outweigh the arguments of maintainer, that renaming would bring a lot of problems and breaking changes.
Hopefully people see now the plight of the Palestenians citizens of other regions in that area, about what the West did to them post WWII.
Looks like a cult-like group of white SJW developers within GitHub/Microsoft have painted themselves into a corner with this suggestion. It will be difficult to get out of this situation without losing face or causing more damage.
I know its the default bit there will be a bunch of people that go in and change it for the sake of virtue only to expect dependent libraroes to manually go in and fix things. Which, wont happen.
We haven't solved lots of computational problems or made the internet and computing more usable/available to everyone, but not to worry, we changed the naming standards on a tool used by a small subset of the worlds population to placate an even smaller subset of loud and vitriolic people.
I agree with the sentiment, but oh sweet summer child. You cant make decisions off of what one person feels. That barely scales up to work with just one person.
https://github.com/search?q=pork <- 800 results
Since such name changes impose a lot of breakage and work downstream, we should find an objective way to designate which ones are necessary. An example could be an ongoing github poll, with the results averaged over years to prevent fads from creating work. A code of conduct could specify that if more than x% of the userbase over y years vote that <word> is offensive, it would be scheduled for deprecation in major version +1 and removal in +2.
No one is asking you to do development work to make it happen. No one is forcing you to update your repositories or change your workflow. You're free to continue using whatever names you want for branches in your own repositories.
If other people want to do this change and are the ones doing it, why spend so much time getting so heated about it?
However, in several OSS projects I follow, it was always corporate steered "open" source devs who "proposed" the change and rammed it through, often against the majority opinion. To further their careers and stroke their egos.
Now GitHub, who still does business with sketchy companies (as does MSFT) does this entirely meaningless virtue signalling change.
Just to show OSS devs who is the boss and that they can do whatever they like with their money.
Could we get some mod action to change the link? Either to Friedman's response (which would show the original question above, since it's a reply) or to something like https://www.bbc.com/news/technology-53050955 ?
Edit: Or if it's a dupe submission of something that's been beaten to death on HN several already, maybe it's not worth fixing.
This feels like "Okay, we know this isn't a big deal, but 60 Minutes is going to run a segment on "Master/Slave" hard drives and Twitter is going to blow up if we don't fix this".
Like spoken elsewhere, the "master" branch is not the opposite of a "slave" branch. Those who are triggered would be showing their ignorance at the etymology, and it seems Github is just getting ahead of an outrage storm.
Nat does have a reply buried in the responses; that should have been linked.
I, know, default, still, some idiot's gonna break something big with this.