this post was submitted on 20 Aug 2024
620 points (88.8% liked)

Showerthoughts

29233 readers
563 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. The best ones are thoughts that many people can relate to and they find something funny or interesting in regular stuff.

Rules

founded 1 year ago
MODERATORS
vatlark@lemmy.world
forkball@lemmy.world
quinten@lemmy.world
Thekingoflorda@lemmy.world
620
If "Master/Slave" terminology in computing sounds bad now, why not change it to "Dom/Sub"? (lemmy.dbzer0.com)
submitted 4 weeks ago by Someonelol@lemmy.dbzer0.com to c/showerthoughts@lemmy.world
462 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
[–] wewbull@feddit.uk 2 points 4 weeks ago (2 children)

Active / passive means something different.

Master / slave means one thing tells the other thing what to do, and the other one does it without question. The slave is not passive in performing the task.

It's a relationship that should never occur between humans, but it does occur with machines. The terms describe what is happening accurately. Other synonyms are approximations and lead to confusion in a field where confusions cause bugs / failures and depending on what you're working on, that could put lives in danger. Do you really want such confusion around the systems of an airliner, where everything has redundancy, master/slave relationships are common and something being passive means "it's only monitoring what's going on"?

You want more Boeings? Shit like this is a good way of getting there.

[–] andrew_s@piefed.social 2 points 4 weeks ago (1 children)

I seem to have stumbled into an argument that people are more passionate about than me. I mentioned I'd seen 'active/passive' used (in computer networking), and in that context, it 'seems alright' (in the sense of actively giving demands, vs. passively accepting them [and doing what it's told, of course])

If someone has made good-faith request not to use certain terminology (like Master/Slave), then I'm generally more interested in finding acceptable alternatives than I am in dismissing their concerns outright. If, at the end of a proper search for alternatives, nothing suitable can be found, then fair enough. I'd question the idea that it's really impossible to find something else though, but - for now at least - I'm sure that Dom/Sub isn't it.

[–] AA5B@lemmy.world 3 points 4 weeks ago* (last edited 4 weeks ago)

Same here - I’m more interested in a suitable alternative than to argue whether they are justified in their concerns.

I don’t think there’s a single right answer though. This terminology is used in many scenarios, each a little different and each with a potentially different answer

  • Most git distributions now default to “main” and some variation of branch. It was a trivial change and seems as meaningful.
  • Jenkins changed from master-slave, to controller-agent (or node). I’m still getting used to it but no big deal.
  • Many DB or service distributed systems changed from master-slave(s) to primary-replica(s) and that also works
[–] zero_spelled_with_an_ecks@programming.dev 1 points 4 weeks ago

Wait until you find out how many programmers don't even speak English. They must not be able to understand any of this if it's so confusing to native speakers, right?

The consequence of updating language is not plane crashes. You need to update the version of the human interaction API that you're using.