[zug_zug]

> What if they then come for my grunts?

Definitely not the point I'm trying to make. The point I'm trying to make is every time we take a safe word and make it a "bad" word we sweep up a lot of people along the way, most of whom in my experience aren't really bad people, they're usually just stubborn, caught unawares, a standup comedian, or taken out of context.

Maybe these language changes should have a 5-year deployment window so everybody gets notice.

I think my other question isn't just where it stops, but when it stops. Is it ever going to be enough words banned and then we're done forever? Because if the answer is "no" then I'm probably not able to side with this change-the-language movement as a good use of our limited political energy.

[eesmith]

Why do you think "master/slave" was "a safe word" in the first place?

The current narrative is that tech industry inherited the dominant white supremacist culture. (To be specific, "master/slave" entered as a tech term in the 1950s there was wide support by whites for the existing laws enforcing white supremacy)

As such, the term was "safe" because those who used it - white people in tech - were also nearly always those people who gain from the underlying dynamics of white supremacy.

Another narrative comes from "Broken Metaphor: The Master-Slave Analogy in Technical Literature" by Ron Eglash" available from https://sci-hub.st/10.1353/tech.2007.0066 :

> ... being unconscious of social mores was a good sign for a future physicist, because physics transcends culture. Perhaps this kind of emphasis on a technical identity is at work here, too, and the master-slave metaphor is attractive to engineers because its free use “proves” that they inhabit a nonsocial or culture-free realm, which is a matter of professional pride

There are other certainly other narratives, which is why I'm asking why you think it was a safe word, even when others do not, and have not for years.

Note that Eglash's paper quotes a Black researcher who had problems with that term back in 1992.

To re-ask your earlier question, whose opinions count on the issue of why a term is "safe"?

You mentioned "a 5-year deployment window so everybody gets notice".

The "notifications" started well more than 5 years ago. Even here on HN, Django changed 6 years ago, at https://news.ycombinator.com/item?id=7801646 .

Drupal changed its terminology 12 years ago, which lead to discussion 6.5 years ago here at https://news.ycombinator.com/item?id=6826918 .

The earliest discussion on the topic was 11 years ago, at https://news.ycombinator.com/item?id=466188 .

When would you consider that proper notice has been sent?

Tell me, do you still use the term Negro? Or did you side with the change-the-language movement on that one? Because the logic you use sounds identical to the logic used to resist that change.

Why use your limited political energy to, e.g., construct hypotheticals against language change when language always changes?

[Macha]

> Tell me, do you still use the term Negro? Or did you side with the change-the-language movement on that one? Because the logic you use sounds identical to the logic used to resist that change.

This has connections with the right of a particular group of people to decide how their group gets named. Wikipedia indicates that "black" was once considered the offensive term: https://en.wikipedia.org/wiki/Negro#United_States . However, most black people today prefer either the term black, or for some Americans, African-American.

This is similar to the issue of whether it's ok to use master/slave to relationships between people, but not whether the usage in tech relates to people or is unacceptable because it parallels historical relationships with groups that in the United States were seperated by race

[eesmith]

I was questioning why it was "safe" to use master/slave in the first place.

Once upon a time it was "safe" to use a number of terms which are no longer safe. I pointed out that some of reasons to oppose the change used similar arguments to what zug_zug used.

You are right - "Negro" is an example of a label that a group decides for itself, and not a good example to bring up. So I'll use two other examples.

Consider "boy". This was a form of infantilization used to remind adult black men that the were junior citizens at best. Civil rights protestors in the 1960s wore signs "I am a man", in opposition to this racist label. But before then, it was safe to call black men a "boy" because if the man were to oppose that use, he would risk being physically attacked and losing his job.

Going back a few decades, white passengers called all black porters "George", after George Pullman - a racial slur that was one of the reasons which lead the porters to unionize. But early on, it was "safe" to call your porter George.

In both cases, I don't doubt there were people who argued against the language change by asking "Is it ever going to be enough words banned and then we're done forever?" Which leads me to conclude that isn't a strong argument.

(See https://ac360.blogs.cnn.com/2008/04/15/understanding-why-you... for a further treatment of both examples.)

zug_zug suggested that it was once "safe" to use the term "master/slave". With those examples in mind, what does "safe" mean? Was it that those bothered or affected by the term have had little power to change things or even speak out until now?

zug_zug elsewhere posed a hypothetical question asking who gets to decide if something is offensive. I turned it around to ask who gets to decide if something is "safe."

Regarding your last paragraph, it also parallels historical relationships with groups elsewhere, as the current discussion of removing statues of South American "heroes" who were also slavers and leaders of genocide shows. South Americans whose ancestors were routinely oppressed via slave culture and white (or white-er) supremacy have little voice in this discussion, but shouldn't be forgotten.

[zug_zug]

I would respond to your points, but I find your tone too accusatory/inflammatory to want to volunteer my energy engaging with.

[eesmith]

So it's okay to construct hypotheticals that distract from actual complaints about the use of "master/slave", but it's not okay to point out seeming flaws in your logic. Got it.