It sounds way less offensive to those who decry the original terminology’s problematic roots but still keeps its meaning intact.
Boss/Minion
If "Master/Slave" terminology in computing sounds bad now, why not change it to "Dom/Sub"?
Submitted 5 months ago by Someonelol@lemmy.dbzer0.com to showerthoughts@lemmy.world
Comments
snooggums@midwest.social 5 months ago
Empricorn@feddit.nl 5 months ago
What’s wrong with primary/secondary or main/alternate!?
SpaceCowboy@lemmy.ca 5 months ago
Primary and secondary are usually peers, where the secondary takes over when the primary isn’t functioning. Which isn’t the same relationship, as the master/slave terminology indicates that if the master fails, the slave will also fail.
Parent/child is probably a better way to describe this kind of relationship.
KillingTimeItself@lemmy.dbzer0.com 5 months ago
well, i didn’t know that computer hardware could be consenting and engaged with with the BDSM community at large.
Personally i just like master/slave because it’s really fucking obvious how things are supposed to work. Outside of that there are some more specific terminologies that work better in specific applications. Leader follower is pretty cringe, but mostly gets the point across. Main and sub is already established lingo in the electrical field from what i understand.
creditCrazy@lemmy.world 5 months ago
Eh it’s just words and they are more common than just computers every time I work on my cars I sometimes might have to bleed the slave cylinder or fill the master cylinder when doing brake work
Malfeasant@lemm.ee 5 months ago
Cars are just full of “problematic” words… Leaking tranny fluid, retarded ignition…
Brkdncr@lemmy.world 5 months ago
Im not having much luck getting top/bottom accepted at my job.
Treble@lemmy.blahaj.zone 5 months ago
Too ambiguous- bottoms are kings.
holgersson@lemm.ee 5 months ago
We’re using server and agent, but im also a proponent of “captain” and “crew”
NicolaHaskell@lemmy.world 5 months ago
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.
realitista@lemm.ee 5 months ago
The thing is that master has a different connotation in IT than server does. Such as in master/slave pairs for fault tolerance.
holgersson@lemm.ee 5 months ago
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.
Lifter@discuss.tchncs.de 5 months ago
Yes, both of those may already be servers
clockwork_octopus@lemmy.world 5 months ago
Main/secondary Prime/secondary/tertiary etc
joyjoy@lemm.ee 5 months ago
Leader / Follower
QuarterSwede@lemmy.world 5 months ago
That’s the one I naturally came up with to.
problematicPanther@lemmy.world 5 months ago
Cargo Mommy module for Rust comes to mind for me.
MinusPi@pawb.social 5 months ago
This is the best thing I’ve ever seen
Redex68@lemmy.world 5 months ago
Why does this have but plug support lmao.
problematicPanther@lemmy.world 5 months ago
you know why
Chocrates@lemmy.world 5 months ago
It is changing, albeit slowly. In git the default branch was changed from master to main.
In high availability we use primary and secondary, or many other versions of the same idea (main/secondary, etc).
Not sure how disks are handled these days but I haven’t seen the master/slave terminology in those since my first CD burner
wewbull@feddit.uk 5 months ago
In git the default branch was changed from master to main.
It wasn’t. GitHub changed.
In high availability we use primary and secondary, or many other versions of the same idea (main/secondary, etc).
Which is fine because in HA it’s about failover, not “who’s in control”.
There are areas where the master/slave terminology is used because the slave does what the master says. It’s “the master has authority” not “if the master dies the slave takes over”.
Different words mean different things.
stephan262@lemmy.world 5 months ago
I prefer to use Main/Sub terminology. It also works without needing to change any acronyms.
KingThrillgore@lemmy.ml 5 months ago
We agreed on Primary/Secondary and Primary/Replica already. Sorry.
untorquer@lemmy.world 5 months ago
Does IEEE have a term for switch or am i about to get intimate with five ethernet cables?
theneverfox@pawb.social 5 months ago
Primary/secondary means they’re all doing their thing, but one is preferred. There’s no instruction going on between them
If you have a primary and secondary web servers, you’ll use the primary first, but the secondary or secondaries are a fallback
If you have a primary and secondary drive, you have two drives, one of which is more important (probably because you booted from it). The secondary could be a copy or just another drive, either way the OS or a raid controller is managing it, one drive doesn’t manage another
Similarly, we have dispatch/worker- the difference between that and master/slave is that they’re different things. A master should be able to work without a slave, and a slave should be capable of being promoted to master - a dispatcher can’t do the work and the worker can’t take over if the dispatch goes down
The funny thing is we don’t use master/slave much anymore, the whole premise is that the slave doesn’t start to do what it does when it starts up. I can’t think of any examples of it in the past decade - other paradigms, with a different relationship and a different name, have replaced it
Lifter@discuss.tchncs.de 5 months ago
Redis, rabbitmq. There are infrastructure where all nodes work but only one node is responsible for properly and timely synchronizing changes, which is a hard problem to solve in a distributed fashion.
theneverfox@pawb.social 5 months ago
That doesn’t really match the master/slave relationship. The distributed instances aren’t slaved to the master. They’re each doing their own thing, but as part of that they have a hierarchical relationship when it comes to synchronization
Distributed computing gets more into the concept of swarms. Each piece is autonomous, and the swarm self-organizes. We made up a bunch of paradigms around this that were basically obsolete by the time we needed them - I think the relationship here is leader/follower, but I’ve never heard that terminology outside the classroom
They’re sharded. It’s like host/mirror, except each mirror is an equally correct part of the real picture
One of them is the leader, but it doesn’t control the rest of them. It just coordinates them
When you get into swarm concepts, like sharding or activitypub, it doesn’t make sense to describe the relationship between nodes anymore. The relationship between any two nodes is “part of the same swarm”. You describe the nature of the swarm as a whole, or the behavior of individual nodes
realitista@lemm.ee 5 months ago
This is true. Warm standby is more or less obsolete in favor of n+1 load sharing.
AeonFelis@lemmy.world 5 months ago
I vote for “OF-Model/Simp”.
TonyTonyChopper@mander.xyz 5 months ago
“Girlboss/Tier3”
letsgo@lemm.ee 5 months ago
Not more wokism! Next they’ll be demanding we stop talking about executing a child!
SkunkWorkz@lemmy.world 5 months ago
Okay but what if I’m in a server room full of switches.
blusterydayve26@midwest.social 5 months ago
top/bottom, clearly.
aodhsishaj@lemmy.world 5 months ago
But which is which when they switch?
elephantium@lemmy.world 5 months ago
Bypass the whole debate, adopt SVN’s ‘trunk/branch’ terms.
AI_toothbrush@lemmy.zip 5 months ago
Wait until a child gets killed, reaped or sometimes even sacrificed
RIPandTERROR@sh.itjust.works 5 months ago
sub should be lowercase. Even at the start of a sentence.
caseyweederman@lemmy.ca 5 months ago
systemd-subd
JackbyDev@programming.dev 5 months ago
You can’t tell me what to do!
Blaster_M@lemmy.world 5 months ago
For IDE drives, Master/Slave is both correct and describes properly the functionality.
Only one device can talk on an IDE channel at a time (one IDE ribbon cable is one channel). The Slave Drive requires the Master drive to be able to connect to the controller. If there is only one drive, it must be designated the Master drive.
We don’t share multiple devices on a single channel anymore - SATA, PCI-E, these techs have only one device per channel (or only a certain number of channels dedicated per device).
The old Master/Slave system was a hack to get double the IDE devices connected per controller channel.
captain_aggravated@sh.itjust.works 5 months ago
I think I could argue that master/slave doesn’t describe that functionality. Does the master drive control the slave drive?
I think a better example is the SPI bus, which has a one-controller-many-peripherals bus topology with two data lines often referred to as MOSI and MISO: Master Out Slave In and Master In Slave Out. (in addition to a clock line and one or more chip enable lines) In this case the controller does literally control the peripherals, which aren’t allowed to put data on the bus unless commanded to. Newer documentation is using the terms COPI and CIPO, for Controller Out Peripheral In and Controller In Peripheral Out. Personally I prefer MOSI and MISO because there’s a definite way to pronounce them; how do you pronounce “CIPO?” See-poh? But it’s something for someone somewhere to be uppity about so sure let’s expand the glossary.
Blaster_M@lemmy.world 5 months ago
The activity light on the Master drive will light up in sync with the Slave drive when accessing data on just the Slave drive. At the end of the IDE lifespan, there was a movement to put the names as Primary and Secondary instead. It doesn’t really describe the relation to how the hardware works, though.
Rakonat@lemmy.world 5 months ago
Top/Bottom Step/Sibling Pitcher/Catcher Thot/Simp Bull/Cuck
prettydarknwild@lemmy.world 5 months ago
even better, top/bottom
JackbyDev@programming.dev 5 months ago
Power bottom/service top erasure!
Localhorst86@feddit.org 5 months ago
but what if i order my master/slave drives the other way around, with the master drive on the bottom?
Ultraviolet@lemmy.world 5 months ago
Power bottom/service top.
ultramaven@sh.itjust.works 5 months ago
Do all pf these things still imply some form of ownership, natural hierarchy? Are numbers racist now? Whenever I type 1 over 2, I think about black people getting whipped. :(
TypicalHog@lemm.ee 5 months ago
If anyone is offended by this CS term - you are a certified soyflake.
lolcatnip@reddthat.com 5 months ago
Looking at your self-description in your profile, you don’t seem like the type to be a raging MAGA idiot, but saying things like “soyflake” really makes you sounds like one.
TypicalHog@lemm.ee 5 months ago
Whatever you say. I hate it when people get offended by the most irrelevant things, and the word “soyflake” seems perfect for those kinds of people. My invention btw - it’s a combo of soy and snowflake that just came to me as I was writing the above comment. Also, I don’t really like Trump. But I also don’t like Harris even more. Trump is also friendlier to crypto. Harris leans way too much into Marxist ideas for my taste and also I hate wars and the deep state (which is more related to the left than the right). But don’t get me wrong, I also hate hyper-religious MAGA low-IQ hillbillys. I REALLY, REALLY like Elon tho. And I like how he is fighting the obvious left-wing bias we have in cyberspace. I’m a neurospicy guy with spicy multidimensional beliefs. Hate me, but that’s how I am, at least for the moment. I’m fairly fluid when it comes to my beliefs. I’m for example pretty deep into a conspiracy arc atm.
Limonene@lemmy.world 5 months ago
I’ve seen “Domain Controller” and “Subscriber” for the sake of plausible deniability.
In the case of SPI, they want to keep intact the names MISO (master in, slave out) and MOSI. So they use things like “Main” and “Sub”.
littlecolt@lemm.ee 5 months ago
Us weebs can use uke and seme.
Hadriscus@lemm.ee 5 months ago
all I read is “ukulele semen”
littlecolt@lemm.ee 5 months ago
It’s not so different, and could involve semen!
ILikeBoobies@lemmy.ca 5 months ago
Don’t know anyone who has a problem with it
I think it was just an ad campaign by Github to capitalize on BLM
untorquer@lemmy.world 5 months ago
Jakeroxs@sh.itjust.works 5 months ago
I’ve had people at the company I work complain about it internally.
bloodfart@lemmy.ml 5 months ago
What the fuck is wrong with computer people?
It’s been primary/secondary and main/secondary in the automotive hydraulics world since at least 2000. I know because my hs car repair class used master/slave and I had to do a double take for a second back in ‘01 looking at the manual before bleeding the brakes on a focus.
Is everything else in the hydraulics world also primary/secondary?
TwentySeven@lemmy.world 5 months ago
I’ve only ever heard the parts of a hydraulic clutch system referred to as master and slave.
I’ve also never heard a brake caliper referred to as a slave.
bloodfart@lemmy.ml 5 months ago
The primary and secondary cylinders are what translate the motion of the pedal into the hydraulic medium and then into physical motion of the calipers. Inside the caliper is the secondary cylinder that moves back and forth when pressed on by the hydraulic fluid.
In brakes it’s usually called primary and piston or master and piston though.
Even the 90 year old guy and the transmission shop didn’t say master and slave cylinder when they were putting new clutch plates in my truck a couple of years ago.
Sam_Bass@lemmy.world 5 months ago
Or child/parent
mexicancartel@lemmy.dbzer0.com 5 months ago
Kill process or sacrifice child
kandoh@reddthat.com 5 months ago
ಠ_ಠ
ultramaven@sh.itjust.works 5 months ago
What? Literally every single relationship can be argued to be “tRiGgErInG”
I’m sick of it, go back to fucking libart class and masturbate to your own utopia
JovialMicrobial@lemm.ee 5 months ago
We use this terminology in the warehouse I worked at to describe smaller orders that were part of a larger order. So you build all the child orders first, then assemble them into the larger parent order.
I wondered if it was ever used in other contexts.
AlexWIWA@lemmy.ml 5 months ago
I think manger / worker is a pretty easy one. It gets hard though because both of these terms are already used for class names everywhere.
Siegfried@lemmy.world 5 months ago
I would go for master and puppets
KillingTimeItself@lemmy.dbzer0.com 5 months ago
i like this one, though i think we should probably go with the properly terminology and use ventriloquist instead of master. We should go full silly.
daddy32@lemmy.world 5 months ago
Master of puppets! And his puppets.
maniii@lemmy.world 5 months ago
Pastor and his muppets :'D Spoonerism got me on this one. :'D