this post was submitted on 20 Aug 2024
619 points (88.6% liked)

Showerthoughts

29805 readers
1169 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

  1. All posts must be showerthoughts
  2. The entire showerthought must be in the title
  3. 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.
  4. Posts must be original/unique
  5. Adhere to Lemmy's Code of Conduct

founded 1 year ago
MODERATORS
quinten
vatlark
forkball
Thekingoflorda
619
If "Master/Slave" terminology in computing sounds bad now, why not change it to "Dom/Sub"? (lemmy.dbzer0.com)
submitted 3 months ago by [email protected] to c/showerthoughts
457 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
[–] [email protected] 32 points 3 months ago (1 children)

It's all good and well until you start working in a repo that has both master and main branches for some reason, and it is not clear which is actually the master/main branch.

[–] [email protected] 40 points 3 months ago (2 children)

Then you're working in an idiotic repo. You could just as well have have a master and an actual_master branch. Similar idiocy.

[–] [email protected] 11 points 3 months ago* (last edited 3 months ago)

It only takes one person to fuck it up. I agree it's stupid, but introducing a conflicting standard increases the chances of someone fucking it up in the name of progressiveness. Needless to say I killed off the main branch that someone one had tried to make to replace the master branch.

[–] SirQuackTheDuck 4 points 3 months ago* (last edited 3 months ago)

A place I used to work at had that.. The corp had rolled out a non-delete policy with something akin to *master, so when someone made a abrv_master branch it got protected and couldn't be deleted anymore.