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

Showerthoughts

29805 readers
776 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
vatlark@lemmy.world
forkball@lemmy.world
quinten@lemmy.world
Thekingoflorda@lemmy.world
618
If "Master/Slave" terminology in computing sounds bad now, why not change it to "Dom/Sub"? (lemmy.dbzer0.com)
submitted 3 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
[โ€“] Chocrates@lemmy.world 11 points 3 months ago (1 children)

It is changing, albeit slowly. In git the default branch was changed from master to main.

In high availability we use primary and secondary, or many other versions of the same idea (main/secondary, etc).

Not sure how disks are handled these days but I haven't seen the master/slave terminology in those since my first CD burner

[โ€“] wewbull 4 points 3 months ago

In git the default branch was changed from master to main.

It wasn't. GitHub changed.

In high availability we use primary and secondary, or many other versions of the same idea (main/secondary, etc).

Which is fine because in HA it's about failover, not "who's in control".

There are areas where the master/slave terminology is used because the slave does what the master says. It's "the master has authority" not "if the master dies the slave takes over".

Different words mean different things.