|
These hypothetical scenarios don't "flesh anything out a little," they distract from the real world in front of us. It's very obnoxious when as a real world person with a real world request, I hear "but what about [insert hypothetical here that isn't actually happening]?" and there's an easy answer: "if that arises, let's deal with it then." I am descended in part from African slaves. I work in tech. I have dealt with, because of my racial characteristics, a variety of micro and not-so-micro aggressions from my coworkers and that's on top of the bullshit I've had to deal with from neighbors and society. All of this causes me to consider walking away to find something where I don't have to deal with as much BS, and that also makes me sure that the diversity issues in tech are not just a pipeline issue, it's an issue of this work environment not being welcoming to people with different backgrounds. All of these issues are additive - few people want to enter a pipeline for hostile working environment in the end, and those that did have to endure constant bullshit in order to be retained. Efforts to use more inclusive language aren't going to fix nearly any of the big problems, but it is very, very nice to see /any/ effort here, given the history of none at all. Seeing the effort makes these space more bearable, and in my estimation that justifies the very, very minimal cost of committing to trying to use inclusive language going forward (as a software engineer I'm not keen on renames for renames sake, but we're not talking about renames anywhere - we're talking about preferring inclusive names for new things). Likewise it's disheartening to see how many white folks want to proclaim that there are no diversity and inclusion issues in tech. |
I'd be quite content to concede renaming master/slave in the linux kernel if that was the end of it. I think what I want to fight against most is the amount of distraction/canceling/fear involved in ever-changing semantic rules. The reason people like me get very hesitant to concede any ground is for fear it would empower even more fear of job security at work (over constantly changing correctness rules).
So you can understand where I'm coming from:
- I worry that this is a slippery slope, and if some places do it, then all places will feel pressure to do it, and be called out on twitter if they don't, and create a huge amount of distraction from actually building good products for the customer
- I worry that this is a slippery slope, and that more words might be included (class, caste, abort, kill, black, white, race, male port, female port, dongle)
- I worry that this is a slippery slope, and that these words in other contexts won't be allowed (mastery, pop culture Britney Spear's Slave4U song, BDSM, Master's ranks in videogames)
(I've seen this in my own lifetime with the word "retard," which used to be the most correct medical term for certain mental deficiencies, and due to a constantly shifting correctness window is now basically worse than "Fuck.")
Now traditionally "slippery slope" is sometimes considered a philosophical fallacy. But perhaps you can say, if the momentum kept going would you be against it? Because if that train didn't stop, I think all the consequences I listed would be much too high a price to pay.