Apparently master / slave goes back more than 100 years. An example is “slave jib”, which was a sail on a sailboat that was permanently set to catch the wind, and was almost always working. Or slave clocks and master clocks, where one primary clock is used to set other dependent clocks.
That’s funny, I’m guessing they thought they were being original and edgy when they merely looped back to the older use. In any case, I’m glad programming lingo doesn’t sound like a klan rally
It doesn’t have to be edgy, it just explains what happens. In db replication, a master holds the truth and slaves repeat it/follow orders. The US has a unique and relatively recent relationship with chattel slavery so people are more sensitive to it now. Doesn’t make it right or wrong, the words mean certain things that describe what the system does.
Your description actually illustrates how terribly inaccurate the metaphor was. If enslaved people imitated the people who enslaved them, they’d be sitting in a rocking chair on a porch sipping lemonade.
The US has a unique and relatively recent relationship with chattel slavery so people are more sensitive to it now.
The earliest record of the master/slave terminology being used in engineering is 1904 by which point slavery was already outlawed in almost every country, including the US. You’re right to say that chattel slavery in the US was a uniquely grotesque form of slavery, but there is no system of slavery in history where slaves are primarily imitating their masters. No matter what anyone’s sensitivity to the topic is, it’s a bad fit for what’s being described.
I believe it was more because in database terminology there were masters and slaves for replication. Version control came under fire soon after.
Things like SPI bus in electronics, too.
Apparently master / slave goes back more than 100 years. An example is “slave jib”, which was a sail on a sailboat that was permanently set to catch the wind, and was almost always working. Or slave clocks and master clocks, where one primary clock is used to set other dependent clocks.
That’s funny, I’m guessing they thought they were being original and edgy when they merely looped back to the older use. In any case, I’m glad programming lingo doesn’t sound like a klan rally
It doesn’t have to be edgy, it just explains what happens. In db replication, a master holds the truth and slaves repeat it/follow orders. The US has a unique and relatively recent relationship with chattel slavery so people are more sensitive to it now. Doesn’t make it right or wrong, the words mean certain things that describe what the system does.
Your description actually illustrates how terribly inaccurate the metaphor was. If enslaved people imitated the people who enslaved them, they’d be sitting in a rocking chair on a porch sipping lemonade.
The earliest record of the master/slave terminology being used in engineering is 1904 by which point slavery was already outlawed in almost every country, including the US. You’re right to say that chattel slavery in the US was a uniquely grotesque form of slavery, but there is no system of slavery in history where slaves are primarily imitating their masters. No matter what anyone’s sensitivity to the topic is, it’s a bad fit for what’s being described.
It sounds precisely as edgy as I thought. Supervisor/grunt. Yodel/echo. I offered one with whimsy and another without as much edge.