this post was submitted on 20 Aug 2024
621 points (88.9% liked)

Showerthoughts

29723 readers
1258 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
    1. NEW RULE as of 5 Nov 2024, trying it out
    2. Political posts often end up being circle jerks (not offering unique perspective) or enflaming (too much work for mods).
    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
621
If "Master/Slave" terminology in computing sounds bad now, why not change it to "Dom/Sub"? (lemmy.dbzer0.com)
submitted 2 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
[–] KillingTimeItself@lemmy.dbzer0.com 0 points 2 months ago (1 children)

Changing our habits is annoying and takes effort, but I dont know why people are so enthusiastic to hang onto a term that refers to a historically dehumanizing relationship that people are still unwillingly subjected to in the modern day.

people aren't enthusiastic about handing onto a derelict term, people just don't care because they don't see a significant enough relation between the two for it to matter, and they know that any given reasonable person will also recognize it as well.

And for that matter, if we're getting rid of master/slave because it's so bad, we should get rid of killing processes, and especially killing child processes. Because those are arguably worse.

[–] Trainguyrom@reddthat.com 1 points 2 months ago (1 children)

we should get rid of killing processes, and especially killing child processes. Because those are arguably worse.

As a parent I have zero qualms about the term "killing child processes" also there's far more actions involved in parent/child relationships in tech than just killing processes.

[–] KillingTimeItself@lemmy.dbzer0.com 1 points 2 months ago

i suppose that's true, but i think that's unfair as the term master/slave itself wouldn't constitute more than the literal power dynamic between A and B as is the intended point of the terminology. It's not meant to be broadly applicable in a generic sense. Though if we were to argue that it would be equally as easy to argue that architecture designs constitute far more than a master/slave style, such that it would remove the significance of the term in a similar manner.