[danenania]

I think the broader question is whether it's a good idea in general to go through terminology or common idioms with a fine-tooth comb looking for unintentional offense or the potential to offend.

It's of course very different when the intention is to offend, as with racial slurs, but when it comes to things like master/slave db, git master, 'sanity check', the masculine/feminine in Spanish, and others that have been mentioned in this thread, you're really talking about a project to 'reform' everyday speech, with no clear boundary on when this project would ever be complete. And really, there can be no clear boundary since 'unintentional offensiveness' is a purely subjective determination that anyone can claim in response to almost any word or phrase, no matter how benign others may find it.

However progressive someone's politics might be (mine are fairly progressive fwiw), this seems like a highly questionable undertaking. There are clear echoes to measures that have been taken by totalitarian regimes in the past, like asking citizens to call out and report each other for ideological transgressions.

Considering this danger and how much it aggravates people to feel that they must walk on eggshells with their words, there seems to be very little practical benefit toward advancing any concrete progressive goals. People not feeling bad seems like kind of a wash since it also feels bad to have your character questioned based on using common/widely accepted terms.

[awb]

I hear what you’re saying about history. I studied abroad in Germany and those lessons are painfully obvious there. But for me the line is drawn at facts and opinion and words in their original historical context. No one is rewriting the definition of “slave”, they’re actually trying to preserve it.

“Master/slave” is a recent manufactured idiom. No one is hunting through dusty books trying to find things to be offended about. As more African Americans enter the field of programming the more apparent it has become how unnecessary it is to use this idiom. It certainly wasn’t coined in a programming context by an African American. It would be inherently obvious to them that it’s not even a good idiom from a semantic view. It’s only because African Americans were absent from those naming decisions that it ever gained traction.

No one is censoring facts or opinions here. They’re simply saying: “hey, now that African Americans are participating more in our programming community it’s become apparent how uncomfortable it is for African Americans to have to use this master/slave idiom that is barely even semantically appropriate. No one is blaming anybody but can we agree to use a term that’s both more semantically accurate and one that all of us including our African American colleagues feel more comfortable with?”.

It’s like if we’re in a public park and I ask you to take turns on the swing. There’s no rule about it and you could say I’m on a power trip trying to get you to give up the swing, or that I’m blaming you for not having noticed that I was getting annoyed waiting. Or we could just take turns and be friends. I want you to stop using the swing so I can use it. You being on the swing isn’t a problem, but acting like I’m oppressing you by asking you to change positions is a bit of a stretch in my opinion. No ones character is being questioned and no one is wrong. But if you say no to sharing the swing because you’re afraid of a slippery slope of me expecting you to share your house, your car, etc. then you’re operating out of fear rather than responding to my actual request. Or, you could trust that when my requests actually inconvenience you, you’ll say no.

> it also feels bad to have your character questioned based on using common/widely accepted terms

I’m know it does. But insisting you’re not offending anyone or have never offended anyone isn’t the goal. No one is perfect. No one can go through life without being a jerk or offending people. The real test is how we respond after we have done so.

If you used an idiom that made some people uncomfortable, just apologize and move on. Don’t be afraid to give up the swing worrying about everything else that might happen later. It’s just a swing and this is just an idiom. Offering understanding and compassion and even an apology costs you nothing but your ego.

[danenania]

I also hear what you're saying, and I agree with your point that a black person wouldn't have come up with master/slave. That said, I've also worked closely with black developers and while I don't want to make assumptions, it's really hard for me imagine them being offended by something like this. It's more like a parody of what a white person who has never spent any time with black people thinks a black person would be offended by.

But regardless, it's not that I'm so stuck on using this specific term. I don't care that much, and primary/secondary is fine, as you say. My point is that many people and groups will have more-or-less equally valid complaints about countless other words and terms, and I don't think attempting to excise all of them from our language is a helpful or productive path to go down. As many anecdotes in this thread have demonstrated, it's not "just a swing" or just a single idiom. It's already starting to snowball into a pretty long list.