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.9% liked)
Showerthoughts
29839 readers
945 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
- 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.
- 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"
I mentally replaced cars with boats recently and it's been inducing nautical terminology everywhere I speak. Cap'n and Crew sounds great for this usage, it feels honest without the shock of great grandpa's heavyweight authoritarianism. I usually wind up stepping down to Spongebob or Pirates to filter out seriousness too, as long as the packet arrives and the replicas are jolly.
The thing is that master has a different connotation in IT than server does. Such as in master/slave pairs for fault tolerance.
Yes, both of those may already be servers
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.