zlacker

[parent] [thread] 10 comments
1. rs_rs_+(OP)[view] [source] 2024-04-29 16:00:57
When, for people pushing this targeting, fascism/bigotry means having a branch in your repo names master I absolutely believe targeting ideas rooted in fascism/bigotry is a bad thing.
replies(2): >>tripdo+U5 >>mrguyo+rm
2. tripdo+U5[view] [source] 2024-04-29 16:23:00
>>rs_rs_+(OP)
On one hand, I struggle to think that people might actually care about switching "master" to "main", as opposed to making wider improvements to inclusivity.

On the other hand, I don't have a strong attachment at all to naming a branch "master" and can easily rename it without a second thought.

replies(2): >>Pareto+m7 >>jwilk+Q62
◧◩
3. Pareto+m7[view] [source] [discussion] 2024-04-29 16:28:16
>>tripdo+U5
> On one hand, I struggle to think that people might actually care about switching "master" to "main", as opposed to making wider improvements to inclusivity.

I thought it wasn't a big issue until I saw how hard one side fought to keep the name "master".

After that I changed my mind and name all of my branches main and give a little push to projects I'm part of to do the same.

Plus, words do have power:

https://www.youtube.com/watch?v=51USLgPWhgc

replies(2): >>zer00e+fn >>lliama+Ny
4. mrguyo+rm[view] [source] 2024-04-29 17:35:45
>>rs_rs_+(OP)
Oh look someone brought a horse carcass to the party.

God forbid a single implementation of popular software change a default in a fairly meaningless way. Especially since the older term hasn't been accurate in software development for like a decade. Does anyone even ship/deploy the "master" branch anymore?

But no, while we should dislike these folks for saying "we don't want a military contractor to sponsor our event", we should 100% get behind "this private company changed a term and I don't like that so obviously they are wrongthinkers"

◧◩◪
5. zer00e+fn[view] [source] [discussion] 2024-04-29 17:39:48
>>Pareto+m7
> I thought it wasn't a big issue until I saw how hard one side fought to keep the name "master".

Master craftsman? Master mold? Master copy? Head Master... Just because this word was used in relation to slavery doesn't curtail its use in language, removing it only serves to focus its "power".

Also, thats not how language works. At all. It is never how language worked. An Australian and an American are going to have a very different reaction to the word cunt.

Candidly, the erasing of words from language for any reason is very 1984, it's a book you might want to read, its a good primer to understanding how control of language is one of the features of fascism. You should probably read up on how linguistic purity was part and parcel of Italian and to a lesser degree German control of the people.

replies(1): >>Zetaph+lc1
◧◩◪
6. lliama+Ny[view] [source] [discussion] 2024-04-29 18:39:16
>>Pareto+m7
> I thought it wasn't a big issue until I saw how hard one side fought to keep the name "master".

They only fight that hard because they know the people fighting to remove "master" are (as a group) acting in bad faith.

On this and many other issues they tend to lie about history and language, extort those who don't comply with threats of sabotage towards their projects and/or careers, and will equivocate and dissemble whenever confronted.

It's perfectly fine want to use "main" rather than "master" (that is probably my preference). And it is perfectly fine to suggest other people do as well. But if you suggest it others and they tell "no" (politely or not), the right thing for you to do at that point is to mind your own business.

replies(1): >>Cthulh+Bd2
◧◩◪◨
7. Zetaph+lc1[view] [source] [discussion] 2024-04-29 22:03:36
>>zer00e+fn
> Master craftsman? Master mold? Master copy? Head Master... Just because this word was used in relation to slavery doesn't curtail its use in language, removing it only serves to focus its "power".

Except none of those examples are relevant comparisons. It's well documented that the reason the default branch name was master traces back to Bitkeeper, which was using the master/slave nomenclature.

> Also, thats not how language works. At all. It is never how language worked. An Australian and an American are going to have a very different reaction to the word cunt.

Master and slave have universal meaning across all English dialects.

If you're going to make an argument against this change on the basis of semantics, at least get your facts right.

replies(1): >>skissa+3t1
◧◩◪◨⬒
8. skissa+3t1[view] [source] [discussion] 2024-04-29 23:56:10
>>Zetaph+lc1
> It's well documented that the reason the default branch name was master traces back to Bitkeeper, which was using the master/slave nomenclature.

Git never had "slaves". And while no doubt that BitKeeper was a significant influence on Git's adoption of the term "master", can you say it was the only one? Are you arguing that Torvalds had never heard of the term "master copy", and that term didn't influence him at all (not even unconsciously)?

> Master and slave have universal meaning across all English dialects.

Even when a word has the same denotation across dialects, its connotations and associations can differ significantly.

Also, certainly for the word "master", there are senses of that word, and derived words, which are more associated with some English dialects than others. In the UK, it is common to call a school principal a "headmaster"; it is very rare in the US; in Australia, it is more common than in the US but less so than in the UK (and mainly associated with private schools). Similarly, "Master" as a title for the head of a university college is traditional in the UK (especially at its most prestigious institutions such as Oxford and Cambridge), I don't think any US universities use it any more.

◧◩
9. jwilk+Q62[view] [source] [discussion] 2024-04-30 07:26:56
>>tripdo+U5
> I don't have a strong attachment at all to naming a branch "master" and can easily rename it without a second thought.

It's easy only if you don't care about all the people who already cloned your repo.

Recovering from remote repos renaming their default branches is no fun.

replies(1): >>Cthulh+id2
◧◩◪
10. Cthulh+id2[view] [source] [discussion] 2024-04-30 08:32:15
>>jwilk+Q62
And yet, branches disappearing is not uncommon. Changing your remote branch name is trivial, but being made aware of it is the problem. It's been a while since this change was done, but if it was still being proposed, the git client saying "oi, this branch changed name" and offering to update things would be a bit more user friendly.
◧◩◪◨
11. Cthulh+Bd2[view] [source] [discussion] 2024-04-30 08:35:27
>>lliama+Ny
I mean in the end it could have just been a polite request.

But a lot of people get very defensive about it, not just for practical reasons but out of fear of the slippery slope or the consequences of a perceived angry PC mob that can utterly destroy their projects and careers.

[go to top]