[Hamuko]

>Do you think you could, with a straight face, explain the nuances of a master-slave relationship in the Linux ecocsystem?

Yes? Master/slave in computers is not the same as slavery in the real life, which is why we can actually do things like switch a server from a master to a slave and vice versa.

[acdha]

Think about how that sounds from the perspective of someone learning this: “we don’t actually use this term following the dictionary definition, we just like keeping it instead of using more accurate words”

What do we lose by switching to precise terms which don’t require everyone to internalize an overloaded meaning in multiple contexts?

[ThrowawayR2]

> "Think about how that sounds from the perspective of someone learning this: “we don’t actually use this term following the dictionary definition, we just like keeping it instead of using more accurate words”"

A bus doesn't have four wheels. An interpreter isn't a human being with language fluency. A bit doesn't refer to the business end of a drill. A port isn't a place where you find cargo ships. People manage to deal with jargon just fine.

> "What do we lose by switching to precise terms which don’t require everyone to internalize an overloaded meaning in multiple contexts?"

The time wasted reeducating (and I use that word intentionally) everyone?

[acdha]

Again, the problem isn’t jargon as a concept but that a few specific terms have negative connotations. “Slave” has baggage which “bus” does not. There isn’t a call to rename the mouse because the name isn’t inextricably linked to a horrible part of history.

As for the cost of switching, one nice benefit to using more accurate terms is that they’re already familiar - if you swap “slave” for “worker” or “replica”, nobody is going to need extensive retraining to adjust.

[neatze]

Just out of curiosity, is chess master gives also bad connotations ?

Do chess pieces color seem racial to you ?

[acdha]

No, because the white and black pieces are exactly the same. This is unlike whitelist/blacklist where you’re specifying a preference where white is desirable and black is not.

[neatze]

They are not same, white moves first, and first move is an advantage in a chess game.

[Hamuko]

What historical baggage does whitelist/blacklist have?

[acdha]

white = good black = bad

Does that seem like a great association to defend when it can trivially be changed with no confusion or loss of meaning?

[dmingod666]

Light = white Darkness = black

[tomp]

Educate yourself please. This narrow worldview is disingenuous and does you no Good.

Black is positive in finance.

[Hamuko]

>“we don’t actually use this term following the dictionary definition, we just like keeping it instead of using more accurate words”

Words can have more than one meaning. Besides, computer terminology has a lot of words that have different meaning in the context of computers than outside of it. We have the desktop, we have the mouse, we have cookies, viruses, buses, servers, clients and so on.

Should we get rid of the "virus" since it can be so easily confused for the thing that is upending the world right now?

[acdha]

“Virus” follows closely with the biological behavior, and it doesn’t have a recent history of being targeted at specific groups.

Master/slave is technically inaccurate in most use and, unlike mouse, it bothers some people. Why are you so attached to keeping incorrect terms when changing will have no impact on your life?

[Hamuko]

I mean, it'll only have no impact on my life as long as I don't have to go and change my master/slave instances to be something else.

And again, it's no less "incorrect" than any of those other terms.

[acdha]

How many seconds will it take you to replace “master” with “primary”? Compare that with the amount of time spent on this thread.

Arguing that the term is not more incorrect, which you have conspicuously failed to do, is missing the point. If you want to argue that a mouse is a confusing name, feel free but also note that usage doesn’t recall brutality in recent history. Masters not only didn’t usually do the same work as their slaves but the relationship was defined by the violence and permanence: your database master doesn’t torture its slaves if they make errors, or threaten to sell their children, etc. When the master died, they were replaced by their children or someone else but never a former slave. If you’re just talking about parceling out work, try to think about why you’re so attached to using “slave” instead of “workers” and how that would call your motives into question.

Using terms like primary/replica (where both do the same work) or controller/worker (where they don’t) both more accurately expresses the nature of the relation and don’t drag in unpleasant connotations.

[Hamuko]

>How many seconds will it take you to replace “master” with “primary”?

It'll take more time than I care to spend on a matter that doesn't have any effect on anything. Unless someone wants to go update all of the servers and all of their documentation for free on our behalf, then fine, sure, have at it.

>that usage doesn’t recall brutality in recent history

This reeks of Americentrism. How is slavery "recent history"? Are we talking about world history or American history?

>Masters not only didn’t usually do the same work as their slaves but the relationship was defined by the violence and permanence

And viruses (the real world ones) are usually not crafted by criminals, yet we call them viruses since the basic premise of the two concepts is similar enough. A mouse has fuck-all to do with a mouse yet we call it that since they have a somewhat similar shape. Now that the wireless mouse is commonplace, this naming is just completely inaccurate and yet it doesn't matter since we can separate the etymology from the meaning.

>try to think about why you’re so attached to using “slave” instead of “workers”

So if I just call a server that has to obey its superior to the T or it's broken a "worker", everything is fine and dandy? That kinda seems like brushing away the issue.

>how that would call your motives into question.

Maybe my motive is that I'm enjoying the status quo (as humans tend to do) and I don't exactly want to start doing all of this renaming just because Americans are upset at it. Or maybe I'm just a massive BDSM fan.

>Using terms like primary/replica (where both do the same work) or controller/worker (where they don’t) both more accurately expresses the nature of the relation and don’t drag in unpleasant connotations.

Killing also has a negative connotation but I don't really feel like I need to spare my processes from this cruel, unpleasant and inaccurate word.

[loco5niner]

> Compare that with the amount of time spent on this thread.

Less time than not changing it.

[loco5niner]

> Why are you so attached to keeping incorrect terms when changing will have no impact on your life?

Master/slave terminology is absolutely accurate here and changing it will have an impact on my life.