620
If "Master/Slave" terminology in computing sounds bad now, why not change it to "Dom/Sub"?
(lemmy.dbzer0.com)
this post was submitted on 20 Aug 2024
620 points (88.8% liked)
Showerthoughts
29707 readers
1769 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
- NEW RULE as of 5 Nov 2024, trying it out
- Political posts often end up being circle jerks (not offering unique perspective) or enflaming (too much work for mods).
- 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
We're using server and agent, but im also a proponent of "captain" and "crew"
The thing is that master has a different connotation in IT than server does. Such as in master/slave pairs for fault tolerance.
Fair enough. Im in devops and the first thing I thought about was Jenkins, where "server" and "agent" fit quite well.
I dont think master/slave is that good of a naming scheme for fault tolerance either, since the "slave" doesnt do work so that the master doesnt have to, but it's rather an active/reserve kind of thing.
But I also admit that using different terms that fit best for every usecase would only cause more confusion than good.
I agree that active/reserve is a better way of saying it, and that's the way I've always said it when working with these systems. Honestly I may have never heard master slave in actual use in 15 years of regularly describing such systems.