This raises some valid points, like the validity of the singular they.
However, I think it is a bit to aggressive in listing unacceptable terms. I understand "off the reservation" because that still has a direct connection to racist origin. There is a defensible argument that it is referring directly to many atrocities that the United States government committed when moving Native Americans to reservations. Fine.
However, whitelist? That's just based off of a color. There's nothing directly racist about it. I'm sure some people feel uncomfortable when the word is used, but there's no logical reason why it should be a problem.
Just because one person is uncomfortable about a phrase doesn't mean the phrase is bad. I once had to leave the room when watching a movie because it had a scene that reminded me very strongly of an traumatic experience I had. However, there is no objective problem with the movie. I am not the main character of the universe, and it is not anyone else's fault that other things remind me of the trauma I experienced.
I don't believe people should be put in environments that are actively triggering, but "native feature"? There is no logical reason to be triggered by that.
This type of rhetoric is problematic because it vilifies people unnecessarily. Killing a process is fine, because processes aren't people. I'm not being violent. If you see the word "kill" and get distracted, that's a problem with your reading comprehension.
All in all, I agree that documentation should not be triggering or have terrible connotations. However, many of the words here are not triggering, and they do not have terrible connotations.
We kill processes, destroy variables, put objects in blacklist, push to a master branch, are we monster ?
Meanwhile in my language, every word has a gender, from table to banana, should I then be triggered by gender neutrality, a concept that "destroy my gender-heavy culture"? :D
Singular they is fine when you dont know the gender, it's true it's weird to favor masculine, or what I see in English favoring feminine. But putting your fav gender in email signature is a bit like... is it truly such a massive problem that everyone must comply and not just people for whom it's not clear ? Im not saying it s not a problem, just is it that massive ?
An interesting feature of some Asian languages (e.g. Japanese, Thai, Indonesian) is that in general they use 1 word (I'll write it as "s/he") to refer to third persons. I wonder how that's influenced kids growing up with the language.
Meanwhile in German they're trying to define RegExp, which is also pronouncable, for gender-inclusive words[1], since they differentiate between e.g. Pilot (male) and Pilotin (female) as well as Piloten (many pilots, in the old days this used to mean of mixed genders, but some people felt excluded) and Pilotinnen (many female pilots).
> An interesting feature of some Asian languages (e.g. Japanese, Thai, Indonesian) is that in general they use 1 word (I'll write it as "s/he") to refer to third persons.
IIRC, that's only true of spoken Chinese, they have different written pronouns for each gender.
> I wonder how that's influenced kids growing up with the language.
In my experience, it only results more mistakes using gendered pronouns (e.g. occasionally swapping he/she), but that's about it. It doesn't result in any kind less gendered outlook or greater acceptance of gender nonconformity or anything like that.
Gabriele Diewald, a linguistics professor at the University of Hanover, disagrees. "The generic masculine is not a grammatical must," she says. "Claims to the contrary are deliberate attempts to continue marginalizing women and other genders."
>> Gabriele Diewald, a linguistics professor at the University of Hanover, disagrees. "The generic masculine is not a grammatical must," she says. "Claims to the contrary are deliberate attempts to continue marginalizing women and other genders."
I mean that's technically true, since it's not even a must to have a number system or much in the way of color categories (or really anything except nounish things and verbish things), but it kind of misses the point.
chairperson or chair over chairman I understand. engineer hours over man hours, sure, makes sense if everybody is contributing.
sister campus or grandfathered seems different, its not gendering a person, but an inanimate object or an action. in the case of the latter, the gender has nothing to do with the person performing the grandfathering. maybe its because the words have an endearing quality to them that substituting them feels like a loss. not sure how i feel about native meaning innate being stricken from available usage. a bridge too far maybe. does the concept of gender really need to be 100% eliminated from all speech?
maybe this comment will age poorly when someday i realize the error of my thoughtprocess.
Interestingly enough, one I think we should get better about IS present in the guide, albeit as part of their description and NOT something you shouldnt say. "When referencing users with disabilities..." The word users sounds like drug users, addicts etc. When talking about people, I have tried very hard to drop the word user from my vocabulary, purely out of respect and politeness. They/we are people. (In IT circles, user almost always has an additional very very slight to heavy pejorative tone to begin with. It implies lesser in some way, or an us/them tribalism, even if people saying it dont understand they are doing it.) The same should go for drug users. They are people.
I understand (to some degree) if someone is willing to enforce things you shouldn't say. Although right to free speech is/should be universal, but it doesn't mean free of consequences of what has been spoken. But I strongly oppose situation and any attempts to enforce what I should say. No. No pasarán. Ni wuja. Claiming power over what one should or ought to be saying is claiming power over what one should or is allowed to think. "1984" of Orwell's says hi.
I read the comments before reading the document and completely expected a 50 page manifesto on the origin of the English language. It appears more like a service organization trying its best to not put it’s frontline workers in what is likely already an uncomfortable position - apply the standard, albeit unfair, criticisms of “dealing with IT.” The brevity the lists makes me think that these are possibly specific instances they’ve encountered.
I’ll mostly use these documents to remind me to use these terms more. What the fuck is wrong with “native”, “housekeeping”, “sanity”? The authors of this surely must be joking.
The mob just needs to be pointed in the right direction, and universities will have to start canceling the term "Master's degree." It seems inevitable, because soon or later the mob will turn its attention towards this, once they've gone after all the low-hanging fruit.
Is low-hanging fruit still an inclusive term? Or it discriminates against short people? Cancel it?
I read a lot of criticism on guides like these. And that makes me wonder, am I the only one that thinks that the 'inclusive' language is simply more clearer?
* blocklist/blacklist, I find blocklist clearer because it does what it says. Same for whitelist
* master/main, same as above, main describes it's function more accurately.
Regarding the genger wording, I have memories as a child where I was confused because for some reason, only the boys where adressed. Not thinking it through, I simply assumed that was intentional. And thus, if a teacher said 'boys, lets go that way!' I would be arguing with the girls since I thought they where not supposed to follow along.
Of course, this is not the case for ALL proposed inclusive language. I simply notice that most of the time, the inclusive alternative is a lot clearer.
Compound nouns in English are usually formed with the first element being a noun or an adjective, not a verb, so the natural way to understand "blocklist" is as a list of blocks, like something you'd find in a file system, or here, for example:
My suggestion would be that if you're allergic to "black" for some reason you go with "redlist", giving you "greenlist" and "amberlist" as alternatives. But I don't personally have a problem with "blacklist".
Not all blacklists are blocklists, and what do you call a greylist?
BTW: Blacklist has nothing todo with skincolor:
~1183 AD Andronicus -> "His memory was stored with a black list of the enemies and rivals, who had traduced his merit, opposed his greatness, or insulted his misfortunes"
> I read a lot of criticism on guides like these. And that makes me wonder, am I the only one that thinks that the 'inclusive' language is simply more clearer?
Even if that were true, you could say the same thing about English spelling reform (which is never going to happen, for good reason).
You cant see in it because there's no light ? Maybe some crude analogy to the first cameras dark chambers ? French wikipedia says it entered our language during WWII to describe enemy military strategies we had to analyze by interacting with them rather than reverse engineer from specs. Black is the color of the night and mystery, white of the sun and openness. I find it insane this is misinterpreted as good/bad, with the mystery color being bad.
We're fighting hard in my company against the same people as usual now brigadding to stop saying black/whitelist, because it does nothing to help black people in America (we're in Asia), who suffer from problems which go well beyond even white people: they entered a cycle of self defeatism where every problem has an external source and therefore solution, to the point of complete apathy.
So when a chinese says "this system is a blackbox" I will not, me a European, tell him to say something else because americans cant fix their shit and now need to pretend me and that chinese guys are part of their problem. It's THEIR problem, they fix it, and for real.
I just got a message from git in my terminal related to "master" branch. Whatever your sexual orientation, gender, race, disabilities FUCK OFF, I'm gonna stick to proper English instead of Newspeak.
The same statement is true for my native language, French, where I'll never use the "écriture inclusive" bullshit except to mock it. Luckily the Académie is with me on this one.
Yeah but the Académie is really just consultative. I will still never say mot-dièse for hashtag.
And that master thing is really stupid, like every population has been enslaved at some point, the word comes from the romans, and it's not like anyone is promoting slavery by saying their master branch dominate their slave branches in git. We also still enslave animals and we can say "human friend" instead of "master" to indicate your relationship with your dog, you're still not asking him for tax advices.
And should we stop saying Maitresse for kids' teachers as well to avoid remiding everyone of slavery...
Where is the uproar over Mastercard needing to change its name now? This is a social media powder keg waiting to explode.
Waitaminute, is "powder keg" still an allowable metaphorical term? Powder keg was a central tool of colonialism and racism in the 19th century. Cancel it?
However, I think it is a bit to aggressive in listing unacceptable terms. I understand "off the reservation" because that still has a direct connection to racist origin. There is a defensible argument that it is referring directly to many atrocities that the United States government committed when moving Native Americans to reservations. Fine.
However, whitelist? That's just based off of a color. There's nothing directly racist about it. I'm sure some people feel uncomfortable when the word is used, but there's no logical reason why it should be a problem.
Just because one person is uncomfortable about a phrase doesn't mean the phrase is bad. I once had to leave the room when watching a movie because it had a scene that reminded me very strongly of an traumatic experience I had. However, there is no objective problem with the movie. I am not the main character of the universe, and it is not anyone else's fault that other things remind me of the trauma I experienced.
I don't believe people should be put in environments that are actively triggering, but "native feature"? There is no logical reason to be triggered by that.
This type of rhetoric is problematic because it vilifies people unnecessarily. Killing a process is fine, because processes aren't people. I'm not being violent. If you see the word "kill" and get distracted, that's a problem with your reading comprehension.
All in all, I agree that documentation should not be triggering or have terrible connotations. However, many of the words here are not triggering, and they do not have terrible connotations.