679
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Aug 2024
679 points (100.0% liked)
Showerthoughts
30049 readers
487 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 2 years ago
MODERATORS
If it’s referring to something like a mother/daughter circuitboard, I’ll use that. If it’s a host/client connection, I’ll use that. If it’s a primary/backup redundancy situation, I’ll use that. And those are just a few examples. There is rarely a good reason to use master/slave nowadays, since most situations already have better descriptors to begin with.
Can't we just change "slave" to "servant" and carry on?
You could but he has a point. The last time I used master/slave was for IDE drives which was 15+ years ago, and even then only because I happened upon a really old system using IDE drives.
The only thing I see left is "Master" by itself, like master branch. But that makes me think of like a jujitsu master which sounds really cool lol.
Yeah, that definition of "master" is different than master/slave from what I can tell. Think the master copy of an audio recording. There are plenty of perfectly legit uses of "master," but there's no reason to use master/slave in this day and age. It was stupid to start doing so to begin with.
Like the Digmaster™.
Especially with how we say releases are "cut" from the master branch, it makes a ton of sense.
you could, but the connotations of master/slave have been integrated heavily over the years, and changing it willy nilly doesn't really accomplish much since we're talking about moving electrons through wires, or light through glass. So i don't think anybody really cares about it at the end of the day.
Realistically though, very little designed architectures these days operate on a master slave meta. At best there's one "primary" and several "secondary" or "follower" nodes behind it. Or some kind of democratically elected process for handling that.
Why retcon something that hasn't been used in over a decade? ATA is dead.
Sure, but if you're gonna change it at all you might as well pick a better metaphor.