621
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
621 points (88.7% liked)
Showerthoughts
31040 readers
1222 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 most popular seem to be lighthearted, clever little truths, hidden in daily life.
Here are some examples to inspire your own showerthoughts: 1
Rules
- All posts must be showerthoughts
- The entire showerthought must be in the title
- No politics
- If your topic is in a grey area, please phrase it to emphasize the fascinating aspects, not the dramatic aspects. You can do this by avoiding overly politicized terms such as "capitalism" and "communism". If you must make comparisons, you can say something is different without saying something is better/worse.
- A good place for politics is c/politicaldiscussion
- If you feel strongly that you want politics back, please volunteer as a mod.
- Posts must be original/unique
- Adhere to Lemmy's Code of Conduct and the TOS
If you made it this far, showerthoughts is accepting new mods. This community is generally tame so its not a lot of work, but having a few more mods would help reports get addressed a little sooner.
Whats it like to be a mod? Reports just show up as messages in your Lemmy inbox, and if a different mod has already addressed the report the message goes away and you never worry about it.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
is that used anywhere but old ide interface disk drives. is it even relevant anymore?
Embedded systems run into this a lot, especially on low level communication busses. It's pretty common to have a comm bus architecture where there is just one device that is supposed to be in control of both the communication happening on the bus and what the other devices are actually doing. SPI and I2C are both examples of this, but both of those busses have architectures where there isn't one single controller or that the devices have some other way to arbitrate who is talking on the bus. It's functionally useful to have a term to differentiate between the two.
I've seen Master/Servant used before which in my experience just trips people up and doesn't really address the cultural reason for not using the terms.
Personally I'm a fan of MIL-STD-1553 terminology, Bus Controller and Remote Terminal, but the letters M and S are heavily baked into so much literature and designs at this point (eg MISO and MOSI) that entirely swapping them out will be costly and so few people will do it, so it sticks around
FINALLY, a comment about IDE drives! Master/Slave is correct in terminology and function for IDE drives.
There’s the “master” branch in git, often named “main” now. In distributed systems, there’s often “master” and “slave” nodes, often named “primary” and “follower”/“replica” now
The master branch in git isn't the same though. It's closer related to the word "remaster." Master used to mean the original document is still used everywhere in tech and outside of it.
Main makes more sense since a master copy should be something that doesn't change in my opinion. But that's semantics...
I mean master on git is a stretch but honestly it would make way more sense for it to be like trunk given the whole branch thing. I honestly never see master and slave node but rather primary and actually usually secondary.
It's used in Cisco networking and Red Hat bonding that I know of. Changing it to primary/secondary IMHO is better and more clear.
I likely have not been in a large enough setup to encounter that. Usually just one router and the bunch of switches.