https://mail.gnome.org/archives/desktop-devel-list/2019-May/...
On the other hand, I second that "slave" is not a good terminology and trivializes real slavery, while a lot of words like "replica" or "worker" are more descriptive in a software context.
I tend to agree that master has a sufficient breadth of meanings that you often can't/shouldn't eliminate its use.
From the Wiki article [0]: "In medieval wars many Slavs were captured and enslaved, which led to the word slav becoming synonym to "enslaved person
https://en.wikipedia.org/wiki/Slavs_(ethnonym)
For the same reasons people argue against abusing terminology like "retard" or "gay", you could argue that using the word "slave" affects people's perception of Eastern Europeans.
The easy one is that we don't want to argue about it, much likes tabs vs spaces - the value for us is in having a standard, not necessarily what the standard is.
The other one is that I spend a ton of time convincing developers to be intentional and deliberate in their naming of variables and functions, and these terms just aren't very intentional. I've had to explain them to several ESL developers because it isn't intuitive.
Allowlist and denylist are great alternatives except they don't read well as verbs
The master/slave naming seems clearly outdated to me and this one is a direct reference to slavery. A better word like replica exists so I'm using that instead. This makes a lot of sense.
On the other hand there's efforts to rename white/black list or the "master" branch on git. I've never thought of these as even being related to racism until people started opening issues on Github projects about that. A master branch in this context is just like a vinyl master, or a master class to me. The final finished product and not any kind of reference to slavery. Am I wrong?