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.
But why master and slave would be a problem to begin with. I'm still using it in git. I think people that have problem with it must have serious issues. It's a US American thing. Makes no sense.
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
Penis / Onahole
I vote for "OF-Model/Simp".
"Girlboss/Tier3"
Bypass the whole debate, adopt SVN's 'trunk/branch' terms.
Top/Bottom Step/Sibling Pitcher/Catcher Thot/Simp Bull/Cuck
We're already using that on the org chart.
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
Wait until a child gets killed, reaped or sometimes even sacrificed
My user name on all my PC's(non root) is literally Master, my PC's are all Slave, slave1, slave2. I will fight to keep them that way. I am also extremely anti slavery for sentient creatures. Words matter in the context of their intent. Dumbing down of the language by forcing alternate uses of a word to mean something other than its obvious intended use is evidence of dilusional minds. Pure and simple, they don't deserve a seat at the table.
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.
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".