this post was submitted on 20 Aug 2024

619 points (88.6% liked)

Showerthoughts

30006 readers

366 users here now

A "Showerthought" is a simple term used to describe the thoughts that pop into your head while you're doing everyday things like taking a shower, driving, or just daydreaming. A showerthought should offer a unique perspective on an ordinary part of life.

Rules

All posts must be showerthoughts
The entire showerthought must be in the title
Avoid politics
- 3.1) NEW RULE as of 5 Nov 2024, trying it out
- 3.2) Political posts often end up being circle jerks (not offering unique perspective) or enflaming (too much work for mods).
- 3.3) Try c/politicaldiscussion, volunteer as a mod here, or start your own community.
Posts must be original/unique
Adhere to Lemmy's Code of Conduct

founded 2 years ago

MODERATORS

vatlark@lemmy.world

forkball@lemmy.world

quinten@lemmy.world

Thekingoflorda@lemmy.world

619

If "Master/Slave" terminology in computing sounds bad now, why not change it to "Dom/Sub"? (lemmy.dbzer0.com)

submitted 4 months ago by Someonelol@lemmy.dbzer0.com to c/showerthoughts@lemmy.world

458 comments fedilink hide all child comments

It sounds way less offensive to those who decry the original terminology's problematic roots but still keeps its meaning intact.

you are viewing a single comment's thread
view the rest of the comments

[+] Sinthesis@lemmy.world -7 points 4 months ago* (last edited 4 months ago) (2 children)

unfair treatment.

We're talking about slavery here.

sick of having to relabel

It's not that hard....to be accommodating.

divorced from the social issues

from your point of view

the code doesn't care

You're right. Call it a controller and agent. I know naming is hard, but we're smart enough to apply our lexicon.

never use the words master or slave ever again? What's next??

Ah, the slippery slope fallacy.

We still use master over main

The default for new repositories on GitHub has been main for awhile now. You would have had to put in effort to change it to something else. You're a stick in the mud.

[–] Tyoda@lemm.ee 13 points 4 months ago (2 children)

The default for git repositories is still master. Not to be the "real programmers only use CLI" guy, but I feel like git init isn't too hipster.

[–] Sinthesis@lemmy.world 0 points 4 months ago (1 children)

...which you get a multiline message telling you to change your ways (Linus doesn't break UX)....every time you init....weird.

$ git init
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>

[–] Tyoda@lemm.ee 3 points 3 months ago

Gonna be honest, I don't think I ever read that. I think I usually just do git status immediately after to see if all's well.

[–] femtech@midwest.social -3 points 4 months ago (2 children)

The default has been main for awhile.

This is the case in our current version of git (git version 2.28. 0). As of October 1, 2020, any new repository you create on GitHub.com will use main as the default branch.

March 2021 for gitlab

[–] Tyoda@lemm.ee 10 points 4 months ago (1 children)

Still the default in git.

[–] Sinthesis@lemmy.world -1 points 4 months ago (1 children)

...but recommended to be changed every. single. time. you git init. https://lemmy.world/comment/11895670

[–] Saik0Shinigami@lemmy.saik0.com 2 points 4 months ago (1 children)

can you point where ANYTHING is recommended at all there?

Cause it simply says that you can change the name. But "master" is the default. That doesn't sound like a "recommendation" at all. But just making people aware since some repositories try to force things like "Main". Almost like the repo you're using might be enforcing shit that Git in of itself doesn't give a shit about.

[–] Sinthesis@lemmy.world -1 points 3 months ago (1 children)

which will suppress this warning

"I'm going to be annoying you until you do something about it" It is recommending that you take some sort of action, that choice is up to you as the user. In fact, the older way of disabling the warning was called advice.defaultBranchName

AFAIK git is still Linus Trovalds' project and one thing he is known for is "you dont fuckin break user space". That is acknowledged in the pull request https://github.com/git/git/pull/921

"will minimize disruption for Git's users and will include appropriate deprecation periods".

Linus is also a fuck-your-feelings kind of guy so deprecation_period == linus_date_of_death. No, I'm not implying Linus is racist/bigot, just that he feels that strongly about breaking user experience.

Git in of itself doesn’t give a shit about.

You're right...and that's why its unbelievable to me how some people are still (it has been nearly 4 years since that PR above) resistant to change this one little thing. This is just the initial branch that we're talking about here. Git doesn't care if you:

﬌ git init
Initialized empty Git repository in /home/xxxxxx/tmp/.git/

﬌ touch foo && git add foo && git commit -am "foo"
[main (root-commit) 9c74dd1] foo
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 foo

﬌ git branch -a            
* main

﬌ git checkout -b bar
Switched to a new branch 'bar'

﬌ git branch -d main
Deleted branch main (was 9c74dd1).

﬌ git branch -a
* bar

﬌ git log      
commit 9c74dd18d493fec727e6ce9e4ba71ed356dd970d (HEAD -> bar)
Author: Butters
Date:   Thu Aug 22 00:14:44 2024 -0400

    foo

[–] Saik0Shinigami@lemmy.saik0.com 1 points 3 months ago

“I’m going to be annoying you until you do something about it”

You call that annoying? Annoying would be not functioning at all unless you choose an choice... or even worse. Go the Github route and specifically force you to use anything other than master.

Git doesn’t care if you:

Right... So why are you attributing Github = Git... When It's clear that's not the case.

[–] Saik0Shinigami@lemmy.saik0.com 8 points 4 months ago (1 children)

Github != git.

[–] Sinthesis@lemmy.world -2 points 4 months ago (1 children)

No shit? Let me guess; you're still using git like Linus intended it to be, decentralized, by emailing each other tar.gz's

[–] Saik0Shinigami@lemmy.saik0.com 3 points 4 months ago* (last edited 3 months ago) (1 children)

No. I'm just not willing to attribute a COMPANY as the sole owner/stakeholder in a protocol that honestly has very little to do with them.

Just because Github does something, doesn't mean that they represent git.

[–] Sinthesis@lemmy.world 0 points 3 months ago

I just used the most popular/known example. Personally I haven't liked GitHub since Micro$oft bought them. I'm ol' school, 25 years in the biz so M$ really really leaves a bad aftertaste in my mouth.

I'll answer your other question in the other thread.

[–] Riven@lemmy.dbzer0.com 2 points 4 months ago (1 children)

Fuck I don't get your downvotes, you're right. I get people want to vent but in the greater scheme of things having to use different words to be a smidge more inclusive isn't that big of a deal or effort considering what some of us do to help our friends be accepted.

[–] warbond@lemmy.world -2 points 4 months ago (1 children)

It's so weird that so many people are calling being accommodating in such a small way "performative" or whatever! I think some people just can't handle change and blame others for it.

[–] orrk@lemmy.world 12 points 4 months ago (1 children)

or it's just literally performative and doesn't actually change anything about the realities of being POC in America other than making (ironically) a bunch of white people feel good about themselves.

[–] warbond@lemmy.world 1 points 3 months ago

Okay then, I'm being performative. I feel better about myself, thanks.