News for hackers. Stuff that matters.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by sillysaurusx on Saturday July 11, 2020 @07:35AM (#23801314)
In an effort to make this thread more interesting:

I think we should get used to the idea of just letting stuff like this happen. What's the downside? Is it really so hard to type "main" instead of "master"?

I get the argument that historically, language has been used to control populations, and therefore it's good to resist attempts to control language. But every time someone complains about master vs main, I can't help but think thoughts that would be rude to repeat.

I recently made a tool for managing TPUs, called tpunicorn (tpudiepie was "clever, but risks legal issues"): https://github.com/shawwn/tpudiepie

The tool lists a bunch of info about the TPUs, including their master IP address. It's the IP of host 0, in charge of TPU configuration.

If someone were to open an issue "Please change master to main," and they were genuine about the request, I'd be like ... ok. And that would be the end of it. It's a s/master/main/g. Sure, whatever.

So, my question for you, dear readers: why not just say ok and be done with it? Is the spirit of rebellion really so ingrained in everyone that this is the battle we want to fight? You can mock it, ridicule it, fight it, but ultimately it's a big bikeshed that people want to paint. Why not let them?

And, you know, maybe it might help. A female dev I know recently expressed frustration about being called a "guy" constnatly. "Hey guys, ..." It's why I say ya'll. She also feels bad about mentioning it, because she doesn't want to be an imposition.

From my point of view, this is a big ball of "whatever, who cares, just do it." But my mind is open: can you convince me that it's important to resist this trend? Without invoking slippery-slope arguments?

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by StevenWaterman on Saturday July 11, 2020 @07:56AM (#23801423)
This is the most reasonable stance imo. If my language is upsetting you, and I can change that for basically zero-cost, I will try my best to do so. I might forget, and old habits die hard, but I'll make a sincere effort.

In the case where it requires effort from other people, such as making breaking changes to an API, I'm less keen, but when it comes to future APIs I'll keep it in mind.

It reminds me a lot of the outrage over trans people wanting to use different pronouns. Just trying to use the pronouns they want you to requires basically zero effort and has a measurable benefit.

I think a lot of the upset around this issue - and I agree here - is that it takes energy away from more important topic. When people are being murdered in the streets, is master vs main the thing we should spend our time on?

While it's a clear false dichotomy, and we can do both, there's a real risk that people will just swap from master to main and feel like they've done their part, ignoring the more serious issues.

Ironically, that becomes a bigger problem the more we debate this. If using main instead of master is just a little thing, you feel the need to do more. If it's a big political stance, you feel like you've done enough.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by rich_sasha on Saturday July 11, 2020 @08:33AM (#23801715)
It is forcing other people to endorse your causes. Language is an open good, with a great many ways to express things. Conventions exist because they let people communicate easily about specific things in concise ways.

The world is full of good causes, there are so many no one can probably list them all. Any person can really only care about so many, a small handful. Similarly, some causes we may actually think harmful and actively oppose. For the vast majority, sane people probably think, hmm dunno one way or the other.

By one-sidedly declaring something terms unacceptable, this is an intrusion on my right to not endorse a cause. Basically, I’m forced to stop using some terms, eg if I want to keep using GitHub etc. And I value my right to leave a cause be, neither for nor against, quite highly. Without it, the world descends into groupthink hell.

As others say, you don’t mind this cause, fine. But others may. I find it harmless but utterly pointless, though offensive to reason and history. Yet I feel an effort to shame me into supporting this cause and endorsing it.

Not to mention, at no point can I hear that this is something people of colour want (whatever that even means, it’s not like everyone who is not white thinks the same). It is patronising that a bunch of presumably white guys working in tech decide what is right and what is not, for the world and for PoC.

Not to mention that the whole debacle is essentially about a massive failure of US society, and yet the whole world is made to participate in this spectacle. Dear Americans, please fund schools for poor Black kids, do outreach programs, scholarships, internships, you know, things that will help underrepresented minorities get themselves out of poverty, before you go on an all-guns-blazing crusade to change English language. The clue is in the name, it is not American property, and certainly not the property of a bunch of unelected founders with egos inflated by VC valuations.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by linza on Saturday July 11, 2020 @09:11AM (#23801952)
Many good points and I agree with all of them except for the last: it's probably not just a US problem although it's the most visible at the moment.

Ironically to me, these efforts are to be more inclusive but I can't see any of that. I can see that the purpose is to evoke these discussions, and in that sense the effort to change the language is not pointless: by having these changes adopted the movement can point at successes to show it was taken seriously at least once.

We are at the opposite pendulum swing now.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by rich_sasha on Saturday July 11, 2020 @11:44AM (#23803012)
I think the problem as posed, and the vocabulary being banished, are unique to the US, though of course racism and discrimination are not.

If I think of other major racial or ethnic conflicts of the recent times (Israel/Palestine, Rohingya in Asia, Balkan genocides, Hutu vs Tutsi, antisemitism, tensions between “original” and “migrant” societies in Europe), none of them are covered by the language being banished here.

Also, the immediate searching for racial undertones in any phrase seems to be a purely American thing.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by sebazzz on Saturday July 11, 2020 @12:14PM (#23803222)
The language is certainly English specific. We call our male teachers in primary "master" which happens also to be the same term as "master used for slave masters.

This makes it also difficult for some people who don't speak English natively to navigate that linguistic minefield.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by tdons on Saturday July 11, 2020 @07:54AM (#23801410)
Let's say your project were written in Java. What if I asked you to rewrite the project in the C language because Java reminds me too much of the colonial period [1] and it is very painful for me because my ancestors suffered during this time.

Would you be open to that request? I mean, whatever, right? Who cares? Just do it. It might help me and perhaps others because to us Java is very painful. Oh, also, if you need an additional reason, Java is sexist because its file header starts with 0xCAFEBABE, another reason to switch to C.

[1] https://en.wikipedia.org/wiki/Java#Colonial_periods

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by viraptor on Saturday July 11, 2020 @08:13AM (#23801566)
The amount of work here is completely incomparable to OP's example of changing few words. OP already mentioned "Without invoking slippery-slope arguments?"
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by helixhelix on Saturday July 11, 2020 @12:29PM (#23803347)
How is that slippery slope? Are you saying only some people have the right to express hurt?
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by eaton on Saturday July 11, 2020 @01:09PM (#23803659)
Technically not a slippery slope, just a false equivalency. Renaming a branch and rewriting a project in another language are in no way equivalent levels of effort, so comparing them based on the principle of "no skin off my back" the original poster articulated is disingenuous.

Saying that the two cases are not equivalent is a criticism of the level-of-effort comparison, not a criticism of a particular people-group's subjective suffering.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by helixhelix on Saturday July 11, 2020 @01:18PM (#23803749)
Oh so ending racism and homophobia in the real world takes too much effort so let's make other people CTRL+H some files instead? That's pitiful and an insult to people who try.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by hrktb on Saturday July 11, 2020 @08:07AM (#23801510)
Similar things happen all the time [0]

An interesting thinking angle to this often “why was it fine before ?”

Was it because nobody knew about that name/word in the first place ?

Was there always incoming requests for change but those were just ignored as baseless, and as the social context changed discarding them is not as easy anymore ?

Was it because the majority of users weren’t offended, but the user base changed enough that offended people’s voices go louder ?

I find a lot of seemingly frivolous or petty word changes have a wider context that are not as simple as it looks on the surface. [0] https://github.com/thoughtbot/factory_bot/issues/1053

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by blub on Saturday July 11, 2020 @08:13AM (#23801565)
I'm not sure it's important to resist this trend, but this is one more way that silicon valley and the people that are part of this culture show how out of touch they are with the real world.

Renaming branches, streets and toppling statues are all cheap gestures that achieve nothing at all but allow those performing them to feel self-important and pose as defenders of the oppressed.

Meanwhile the oppressed would like to have at least their freedom, a roof over their head, a secure job that allows them to make a living and a modicum of respect from those around them. But no, too many people in the US (and elsewhere) can't have that because it actually requires effort, at least more than running some git command or posting a tweet.

This is such an empty and disrespectful gesture that it makes a mockery of what it means to fight against discrimination.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by mercer on Saturday July 11, 2020 @12:25PM (#23803310)
Your comment basically boils down to 'how dare others request empathy'. I find that childish. How do you 'know' for a fact that their concerns are 'cheap gestures' or 'empty' or 'mockery'? And if you don't know this for sure, and accommodating is cheap, why not? Making a big deal of it strikes me as immature.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by blub on Saturday July 11, 2020 @01:33PM (#23803951)
I have no idea what recipe you used to boil my comment but I wrote it like I meant it, so address it like that.

For one I meant that the gestures are literally cheap: it costs almost nothing to send a tweet or invent some guidelines.

They're also empty because they don't have any effect in the real world.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by mercer on Saturday July 11, 2020 @01:54PM (#23804143)
How don't comments or tweets have an effect in the real world considering this 'cancel culture' hubbub and all? apparently you can get fired for tweets?
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by blub on Saturday July 11, 2020 @04:10PM (#23805463)
Assuming that the goal was to reduce discrimination and racism, getting random people fired does not help achieve the goal and hence has no effect.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by dwaltrip on Sunday July 12, 2020 @02:22AM (#23809308)
Perhaps I’m somehow mistaken, but to me it seems like a very meaningful act to take down statues celebrating those who fought to keep people enslaved
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by viraptor on Saturday July 11, 2020 @08:02AM (#23801460)
Pretty much agree with all that. There are two places where I do fight against it is where someone references external established standards/documents. For example if you're using SPI, the devices are master and slave. Until SPIv2 changes the naming, software using it should match it. Same for changing public API without leaving backwards compatibility names.

The second one is if the name is already massively spread and a known brand which just can't be "renamed". Like in Rubocop case - you can't rewrite every mention on the internet. If you're going to kill the brand... it's just not worth it.

Otherwise, either do a quick change, or ask "if you care enough, please submit a PR" and just be done with it.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by scrollaway on Saturday July 11, 2020 @08:16AM (#23801587)
What's the Rubocop case?
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by viraptor on Saturday July 11, 2020 @08:20AM (#23801611)
https://github.com/rubocop-hq/rubocop/issues/8091

Proposal for removing "cop". TL;DR: Rejected by author because the name is so established as a brand it would take massive effort to change.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by mercer on Saturday July 11, 2020 @12:27PM (#23803328)
Yeah, that one seems reasonable to me too. I am somewhat cop-averse (at least in the US), but the justification for keeping the name are reasonable.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by ThrowawayR2 on Saturday July 11, 2020 @09:21AM (#23802019)
If software developers are opposed to security theater (https://en.wikipedia.org/wiki/Security_theater), then it's not unreasonable to be opposed to "equality theater" as well, which is what language policing is. It's just not a worthwhile use of time, however minuscule.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by eaton on Saturday July 11, 2020 @01:02PM (#23803606)
This is what's felt disingenuous about a lot of the pushback energy, at least to me. The conflict is framed in terms of: "People who say they'd be more comfortable if X were changed to Y," and "People who say X vs Y is meaningless… but spend inordinate amounts of time arguing that branch changes and other relatively inconsequential change is _literally the death of freedom_.

If it doesn't matter, it's low-effort, and the change results in an environment that's more comfortable for some people, it seems like a pretty straightforward equation. Anyone who wants me to oppose that kind of change is implicitly arguing that it does matter, and the current state is the better one… without bothering to make a case for it.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by ungawatkt on Saturday July 11, 2020 @08:06AM (#23801498)
Basically this. It's changing the labels, at worst it doesn't help anything, but maybe it does, and it costs little to nothing in practice (imo by the time you're in workflows where the terminology matters, you've waded through enough semantic BS that it's just a drop in the bucket). And just maybe using manager/worker instead of master/slave makes someone's day better, or (getting personal) is one less reminder that "hey, don't forget, you're the only black person in the room, get ready for an awkward look". same as not getting called a guy when you're not is usually a good thing.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by realusername on Saturday July 11, 2020 @07:45AM (#23801364)
I'm personally against those changes, I can explain my thoughts if you want. I weight the upsides & downsides of the changes.

There is basically zero upsides I can see to this changes whereas it just makes terminology more difficult to learn for beginners. Coding is already a very difficult field, there's no need to make it harder.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by kqr on Saturday July 11, 2020 @11:23AM (#23802819)
Clearly there are upsides: some people are more comfortable with the suggested terminology.

Why is "blocklist" or "denylist" harder to learn for beginners than "blacklist"? If anything, the approved terminology seems easier to learn, if you ask me.

It sounds like your argument is not so much about beginners learning for the first time, but experienced people needing to learn a different word for a concept they already know. I'm fairly sure I can learn what "blocklist" means with minimal effort, but perhaps that's a difficult word for some people.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by realusername on Sunday July 12, 2020 @12:16AM (#23808754)
> Clearly there are upsides: some people are more comfortable with the suggested terminology.

Is there some study about that? The concept of people being offended by these terms itself sounds ridiculous and I have a very hard time to believe it, having at least a beginning of a proof would maybe help here.

> It sounds like your argument is not so much about beginners learning for the first time, but experienced people needing to learn a different word for a concept they already know. I'm fairly sure I can learn what "blocklist" means with minimal effort, but perhaps that's a difficult word for some people.

It just creates a balkanization in IT, both terms will be used simultaneously.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by helixhelix on Saturday July 11, 2020 @12:31PM (#23803368)
How many people feel uncomfortable with this terminology and who are they? What about the people who feel uncomfortable with the new terminology instead (the majority)?
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by mercer on Saturday July 11, 2020 @02:00PM (#23804188)
The majority don't really care and have other things to worry about. Then there's a few who care and the only explanation I have for that is that they're either racists or over-sensitively engaged with some political narrative.

I mean, really, I've asked a number of my friends who aren't too politically inclined and their reaction is a shrug. They don't really get it but they don't care to figure out why and they don't care either way because they've got stuff to do.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by helixhelix on Sunday July 12, 2020 @05:26AM (#23810096)
Shows how little experience you have with asking people why they disagree with these changes, if you shrug off rationalism as racism.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by AlexTWithBeard on Saturday July 11, 2020 @08:13AM (#23801557)
> What's the downside? Is it really so hard to type "main" instead of "master"?

Is it really hard to say your prayer before the dinner?

Is it really hard to never ever eat pork?

Is it really hard to bow to every police officer you meet?

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by kqr on Saturday July 11, 2020 @11:27AM (#23802845)
In a situation where I would knowingly discomfort people by eating pork or not saying a prayer, sure, I just might modify my behaviour to be a nice person. Clearly it means something to them, so why not be considerate for such a small cost?
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by sebazzz on Saturday July 11, 2020 @12:09PM (#23803186)
"Please stop eating pork, as an vegetarian it offends me."

Will you now stop eating pork? If not, at which point do you decide you will alter behavior for someone else. How do you make that judgement?

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by kqr on Saturday July 11, 2020 @04:21PM (#23805567)
If someone asked me during a meal to refrain from ordering pork for that reason, then sure I would. Why shouldn't I?
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by sebazzz on Sunday July 12, 2020 @01:24AM (#23809068)
That is a specific situation - what about the parent situation which implied to be more general.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by AlexTWithBeard on Monday July 13, 2020 @08:15AM (#23819906)
Even when this someone is not from your dinner party?
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by ThA0x2 on Sunday July 12, 2020 @10:37PM (#23816659)
The fact that the West eats pork is discomforting to Muslims and Jews. Please modify your behavior to be a nice person and stop eating pork. It's such a small cost after all.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by disposekinetics on Saturday July 11, 2020 @12:07PM (#23803178)
If you give an authoritarian who wants to control you an inch they run you for a mile. It is important to stand your ground in the petty cases so they never get to their true goals.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by mercer on Saturday July 11, 2020 @12:29PM (#23803345)
Their true goals I suppose being putting you in a scary gulag?
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by disposekinetics on Saturday July 11, 2020 @12:51PM (#23803513)
We don't have to know the specific goals of these authoritarians to know from history that giving into people who want control is a bad idea.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by nyberg on Saturday July 11, 2020 @10:32AM (#23802469)
> I think we should get used to the idea of just letting stuff like this happen. What's the downside? Is it really so hard to type "main" instead of "master"?

> If someone were to open an issue "Please change master to main," and they were genuine about the request, I'd be like ... ok. And that would be the end of it. It's a s/master/main/g. Sure, whatever.

Not at all, it's just a question of who will pay to update all code and documentation to follow the new naming standards. That's not only the documentation of the project in question but also resolving issues when refering to external sources which also use master/slave terminology such as the MBus and related tooling.

> Why not let them?

Will they pay someone to make the changes or do they expect smaller places to shell out money to fix a non issue to avoid being associated with something they've never had any relation to? No? No change unless they either do the work themselves or pay for the cost of changing it.

> From my point of view, this is a big ball of "whatever, who cares, just do it." But my mind is open: can you convince me that it's important to resist this trend? Without invoking slippery-slope arguments?

There isn't really much of an argument for implementing it other than being pushed into exile by others if you don't. Resisting it would mostly come down to the cost of yet another cosmetic change that does nothing other than cost hours of work with no real reason than some being "offended" by well established terms.

In the end, this is a change where I just don't see the merit of. In the end it seems to be the practice of banning being easier than understanding what it's actually used for and comming up with a solid argument for change. It's not the burden of those sitting on `master` branches to explain why not but rather those suggesting this change to provide at least something which hints to the change being worth the effort.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by simias on Saturday July 11, 2020 @08:11AM (#23801545)
That's my stance as well. I thought the "master/slave" thing made some sense, it was very loaded vocabulary in what should be purely technical lingo. The whitelist/blacklist thing seems a lot less meaningful to me and a bit overzealous but... meh, who cares. The churn is fairly minimal anyway and fighting it would turn it into an even bigger deal which is not what I want.

At best it'll help some people feel respected and included, at worse it'll do... nothing at all.

I'm also happy to see some somewhat level-headed discussion on these topics on HN, lately every time that stuff was brought up the thread would descend into 4chan-lite immediately. Very embarrassing. Maybe it's because we're on a weekend and people are better rested.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by pjc50 on Saturday July 11, 2020 @08:08AM (#23801516)
I'm reminded of something a moderator of a Twitch channel said recently: they had a policy of banning people for complaining about "pronouns".

For the first few weeks this resulted in a lot of fights, but after that the moderation load as a whole was much lower. In effect, they'd found a means for flushing out those who liked provoking others and a clear rule to ban them with. There isn't a large number of such people, they're a tiny but very loud minority.

Codes of conduct have a similar effect. Someone who complains about the mere existence of a code of conduct is pre-announcing that they like annoying or upsetting other people.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by PostOnce on Saturday July 11, 2020 @08:21AM (#23801623)
And having a code of conduct is a sign that this place is so terrible so regularly that it needs a code of conduct to get people to be civil to each other.

OR, everyone in power is a satirical HOA tyrant type character whose primary hobby is rule-making.

Either way, code of conduct is also generally code for grumpy and to be avoided, lest your time there be spent in moral lectures and petty arguments instead of on whatever the ostensible topic is.

I try to go places where people get along without a codified list of civil behaviors, because then I know I'm in the company of adults.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by Huggernaut on Saturday July 11, 2020 @08:28AM (#23801673)
More likely the uncivil behaviours go unnoticed by you.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by nyberg on Monday July 13, 2020 @01:53AM (#23817536)
This kind of thing is what I see all the time and it's just exhausting at this point. One is always apparently blind as quick as they present a view of things not always being so bad without a legal document to direct behaviour. It's the assumption that people are barbarians by default and need to be herded like cattle rather than the possibility of them having some decency at all that I find the most saddening. You can have a welcoming and inclusive community without such a document and having one doesn't make you much more inclusive as it's people rather than the document that provide what you're asking for.

Trust until broken and gratitude for upholding good values is the path to a better community along with giving a chance to do better. Quick punishment only leaves a sour taste for everyone.

Also, a good rule is to wait 5-10 minutes or more and see if what you've written aligns with what and how you want to say it or at least expanding on your point a bit further to avoid being misinterpreted.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by mercer on Saturday July 11, 2020 @12:40PM (#23803432)
YES!

It reminds me a bit of the many discussions I've had with far-right buddies of mine about IQ. The topic would be IQ in relation to 'ethnic groups' or 'geographic regions', sub-saharan africa being a popular topic for them. Also Ashkenazi Jews and their (apparently?) higher IQ. They really found those interesting, without making judgments, of course.

And while for the past decade or so I've been happy to talk about IQ, it's meaning, it's implications, ethical or otherwise, there was something about these conversations that felt off to me.

Then at some point I realized that what bothered me was the focus and specific complaints, the 'meta' aspect of these discussions. Stuff like "we hide IQ research because it might expose ethnic differences and the leftie researchers don't like that", more explicitly, but generally it was just the fact that these friends seemed obsessed with IQ in relation to ethnicity.

I realized that, having studied psychology but also always having had an interesting in the topic of IQ, until recently there were SO many other interesting questions to discuss. What 'is' IQ? How does it relate to what we consider 'intelligence'? Why the Flynn effect? Why are people with high IQ just as susceptible, or even more, to manipulation and marketing? How does IQ correlate to empathy, and how does that correlate with how our moral compass works? etc.

IQ in relation to race, no wait, ethnic group, was just one of those interesting questions. it felt like a more sensitive topic to discuss, especially in its implications, but it was just one of many.

I realized that the fact that these friends focused on this ONE topic at the expense of all the other ones (and often complete lack of knowledge) was in itself signifying something (and in my opinion not always racism, but inevitably racism if you followed them to their sources).

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by dilap on Saturday July 11, 2020 @01:40PM (#23804013)
It's an important question, though. The belief underlying lots of policymaking right now is that any inequality of outcome must be due to bias. If that's actually untrue, then we're going to end up trying to eradicate something that doesn't exist, with likely negative consequences.

I would argue that the increasing trend to eliminate objective admittance criteria to schools are an example of this. (I think standardized testing is a huge boon to socio-economically disadvantaged kids; it certainly was for me.)

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by mercer on Saturday July 11, 2020 @01:53PM (#23804138)
Oof, well, I don't entirely disagree with that.

I will say as a general statement that I do think there are systemic biases against various minorities (or women in some cases, who aren't really minorities in the counting sense at least), and that some 'solutions' definitely don't help.

But my main point was that elevating this complex problem, which, again, is well worth having nuances discussions about, and which, to my knowledge is generally very much discussed in 'intellectual circles'. well, it's raised to red-scare totalitarianism-is-right-around-the-corner levels of discussion that I believe cause more harm than good.

For me the debate between Jordan Peterson and Slavoj Szizek confirmed and illustrated this view. if you haven't seen it, watch it and observe the dynamic. The expectations that in particular Peterson had of this 'Marxist' he was finally going to talk to. It's fascinating how often they agree, but also how bad his hyperbole-pretending-to-be-intellectual shit falls apart.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by dilap on Sunday July 12, 2020 @03:29PM (#23814060)
Thanks, interesting points. I haven't seen the Szizek/Peterson debate; I'll check it out.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by helixhelix on Saturday July 11, 2020 @12:36PM (#23803403)
That's just an assumption on your end. I'm not the one going against social norms and making people pay special attention to me or else I cancel them. If anything, these codes of conduct are to LGBT what gay parades are to homosexuals like Alan Turing.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by mercer on Saturday July 11, 2020 @12:43PM (#23803448)
> If anything, these codes of conduct are to LGBT what gay parades are to homosexuals like Alan Turing.

Righting a horrible wrong? I'm not aware of gay parades re Alan Turing but I sure as hell commend any efforts to right that particular wrong! or even just make people aware of it.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by helixhelix on Saturday July 11, 2020 @12:48PM (#23803488)
I mean it as a movement that is meant to louden people's voices but ends up perpetuating stereotypes and slipping homosexuals who don't stand out and aren't flamboyant into such a profile.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by mercer on Saturday July 11, 2020 @12:49PM (#23803499)
In the spirit of truly wanting to find understanding: could you elaborate? I found the initial comment difficult to fully get in the first place (which might be entirely my fault!).
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by helixhelix on Saturday July 11, 2020 @12:52PM (#23803532)
I explained my entire point of view. As an ESL I can't do better. Thank you.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by mercer on Saturday July 11, 2020 @01:41PM (#23804030)
I'm an ESL too and you did a truly terrible job 'explaining'. You just threw out a bunch of sentences that - I think - makes somehow light of Alan Turing's suffering for being gay. I was hoping you could explain further so I wouldn't stick with that conclusion.

EDIT: So I guess you're saying flamboyant gays ruin it for those who pretend to be straight in all the right ways well enough?

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by sebazzz on Saturday July 11, 2020 @12:04PM (#23803164)
> they were genuine about the request

Who are you to make a judgement about that? How do you make that judgement? Or would it only happen if it is about links to racism. If I say I'm offended about you having a Christmas hat as icon during Christmas, who are you to say no?

And this is actually happened at the VS Code repo - someone felt offended about a Christmas hat. I think they eventually decided he was a troll - but what if he was actually genuine?

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by mercer on Saturday July 11, 2020 @12:21PM (#23803268)
I very much agree with the person you're responding to, and this example would be one I similarly wouldn't mind correcting.

Sure, I don't have issues with Christmas hats and probably I'd wait to hear from at least more than one single person. But changing the icon knowing that it made one of my users happy would be trivial. Sure, refusing to would be my right, and perhaps it would only 'lose' me this one user. But deciding to change the icon would make me feel warm and fuzzy because I removed an obstacle to probably a few users. Because if I squint I can sorta see their point.

Of course there are limits and of course these are fuzzy. But I can totally see how multiple people might find a Christmas hat offensive, even if I personally think it's really silly. Anything else than making a call that doesn't cost much and alleviates others' concerns feels to me like being petty for political sakes. I don't like that.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by scrollaway on Saturday July 11, 2020 @07:51AM (#23801399)
I wrote a comment on tildes addressing that exact question about where the harm lies: https://tildes.net/~comp/pra/replacing_potentially_insensiti...

In short there is no harm in the change itself, but rather in the perception by others of where people choose to waste their time rather than productively address root causes.

The harm is that changes like these don't actually help, and they are perceived negatively by people at large. This increases the divide and is a net negative.

And if you think I'm wrong you need only look at the comments here.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by craigsmansion on Saturday July 11, 2020 @09:02AM (#23801906)
> I think we should get used to the idea of just letting stuff like this happen. What's the downside?

Because in the end, actual progressive left thinkers could end up in a rice paddy with a tyre iron in the neck.

This terminology platform seems to be very much pushed by those who feel they should be leftist intellectuals, but who don't quite cut it in the thinking department so instead they just grab the microphone and make up in volume what they lack in depth, labelling anyone, regardless of political view, who speaks out against them as the enemy of progress.

Long term such actions are detrimental to the development of an actually better and fairer society.

Short term it's just grating to see the very real plight of certain minorities being abused by opportunists for their own selfish ends, again.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by skytreader on Saturday July 11, 2020 @08:13AM (#23801564)
I used to share your perspective that this isn't worth getting up-in-arms about until recently (ahem, GitHub) when this kind of political correctness has been enforced to ridiculous levels.

I might sound over cynical in the following but, in as much good faith as I can muster, let me explain why I find this annoying:

> What's the downside? Is it really so hard to type "main" instead of "master"?

This might be a bit specific to GitHub but consider that it's not so much about _typing_ "main" vs master but more about all the automation scripts that will break just so some company can signal their virtue.

Maybe invoking a bogey man here but I would really HATE it if that recovery script that's been known to work for ages suddenly fails to work in one of those 2AM emergencies that always happen just because `NODE_ASSIGN_SLAVE` has been renamed to `NODE_ASSIGN_SECONDARY` without backwards compatibility.

> why not just say ok and be done with it?

This is put succinctly by another (sarcastic) comment here: "I guess we'll call this a win and continue to ignore the root of the problem". I would argue that people who legitimately care about the social issues changes like these claim to address should also be wary about this over-political correctness, else they risk failing to achieve the actual changes they clamor for inn exchange for all the low-hanging fruit.

The problem with shallow CSR lip-service like this is that it is distracting and cheapens the conversation on the issue. And by embracing cheap talk we are letting entities (not necessarily pointing at anyone) get away from taking actual and meaningful action to address the problem. These virtue-signalling changes allow these companies to have something to show for in terms of social responsibility without actually doing the difficult bits that would actually matter.

Because I realize GitHub is now part of Microsoft, let me point out that it costs them next to nothing to change the terminology used in their products but meanwhile, they make money off "innocuous" product offerings like bleeding-edge facial recognition without second thought. Who cares that it is invasive to privacy or can be used to exacerbate discrimination against at-risk social groups, so long as it does not use the term "master" right? (Correct me if I'm wrong and being over-cynical and that Microsoft has dropped these contracts. One of the few times I would really love to be proven wrong.)

Acknowledging that this thread is about Linux, specifically, which is non-profit. The points above might not apply to them.

> ultimately it's a big bikeshed that people want to paint. Why not let them?

In conclusion, as you've invoked the bike shed imagery anyway, the problem with this is the same as any other bikeshedding argument: we can paint the bike sheds but meanwhile the police who are supposed to protect the village are held to no accountability which is actually the reason why we called this homeowner's meeting in the first place isn't it?

How about we paint the bike sheds once we've held the police accountable? Those bike sheds aren't killing anyone, aren't discriminating, and I'm just wary that the conversation will stop because we've appeased the reward centers of our brains because we've already "achieved something" through the bike sheds. It would be absurd that in the minutes of the meeting on police brutality the resolution would be "We painted bike sheds!".

Besides all that time we leisurely spend painting those damn bike sheds can actually be used for more productive things, not necessarily on the social activism front.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by boltzmann_brain on Saturday July 11, 2020 @08:05AM (#23801488)
The problem is this is a slippery slope. Where does it end? Today it's "master", tomorrow someone will be offended by something else. Do we need to accomodate every offended person? I don't think so. This is insanity.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by helixhelix on Saturday July 11, 2020 @12:21PM (#23803269)
We go extra lengths and try to formalise subjectivism but gain nothing. It's always anecdotal evidence or sensationalism that provokes such changes to be made.

In fact, why don't people for these populist changes express some arguments that aren't based on using "misrepresented" people as shields and scapegoats? In fact, using minorities to perpetuate your personal cause is misrepresenting them as weak and powerless.

All this talk about just accepting it is defeatism. You're promoting defeatism. Are you so scared to bounce back that you wish to ostrich your way out of any pressure?

Why, yes, it is too hard and unnecessary to write main instead of master, or any of the hundreds of completely arbitrary changes made with, I repeat, zero net measurable gain.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by eaton on Saturday July 11, 2020 @01:06PM (#23803638)
Let's say I'm standing in the aisle at the grocery store, and someone asks me to step aside so they can pass. It takes minor effort on my part — inconsequential but more than simply standing there — but makes things better for them. Is simply doing so a defeat? Have I been defeated? Is saying, "Yeah, I'd move a step or two to the left, no biggie" defeatism because the movement does not bring "measurable personal gain" to my life?

That feels like a sad, thin way of living life.

Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by helixhelix on Saturday July 11, 2020 @01:21PM (#23803781)
I can also make analogies. It's like asking a baker for carrot cake every day and when he finally makes one, you explain you were merely thinking of other people. Nobody else has asked for carrot cake but it made you feel special for a moment even though you know it wasn't interest in people's eyes.
Re:Linux 5.8 Formally Adds the Inclusive Terminology Guidelines by mercer on Saturday July 11, 2020 @01:37PM (#23803985)
I fully agree with your perspective, and thanks for putting it in words more succinctly than the word-vomit I'm going to put on the internets.

I've had a ton of discussions with friends who are more right-wing, some of them probably 'alt-right' (one of them overtly racist).

and one of the things that I've found hard to discuss is the 'meta' observation that they're all up in arms, outsizedly outraged, about particular, and somewhat peculiar things.

In this case it's BLM (which, sure, I am totally fine with discussing the Marxist aspects of some of this movement! It's probably true, but hey look up the history of women's and civil right's movements!), but previously it was #metoo and I forget whatever came before that. I think it was being able to point out the higher incidence of crime among minority <x>. Which was sort of taboo before that (70s or 60s, over here? but not really of course.)

In all those cases it was borderline-violent outrage that was their first go-to, is what stood out to me.

I'll never forget sitting in a car with a friend of mine, heading to my first-ever Jordan Peterson talk (which I have to admit in hindsight, was much less bad than I expected because he seemed to realize that he was a speaker at a crypto-white-supremacist forum and really seemed to try to counter that).

This was at the height of the #metoo 'craze'. I think Weinstein's transgressions had just gotten out. I didn't bring it up, because I knew what would happen, but somehow the topic came up.

His first reaction, almost reflexively, was to be negative about all of it. Strongly and emotionally. He expressed concerns of a future where men would be jailed just because they were accused of something without due process (shades of 'outrage culture' being just one step removed from gulags, which is popular on HN now?). how he had a female friend who described a situation as 'forceful' toward her and how it implicated the dude in the situation and /that/ was the bad thing. Never mind that this one particular friend was notoriously unstable and had been diagnosed with some serious mental health issues.

And I just sat there stunned, at first, because what had been on my mind was the many close female friends who had, for the first time, probably emboldened by the #metoo thing, told me avalanches of stories of harassment, and an avalanche per individual woman: overt sexual abuse, constant harassment, and the like, that I thought I was aware of but never realized was so common to them, to the point where they'd stopped mentioning it and just made dark jokes about it. overt rape was not rare in these stories.

To be clear, I think there are many issues in current-day male-female relationships that also raise concerns that might warrant empathy for said males. I mean, even if we don't care let's not it's particularly fertile ground for fascism.

I also think that some of the stories I've heard are more a sign of communication issue or projected trauma than what they claim about the males that were 'perpetrator' in these situations.

I also believe that there are aspect of current-day society where the quintessentially privileged 'young white male' pulled the short end of the stick and I think this is a real problem. I know men who have been raped and I've had my own experience that I'd describe as 'difficult' and 'not really voluntary' and that mirrors experiences that have been describes as rape. And the fact that I can't say I've been raped is problematic.

I know a shockingly large number of 'privileged white males in their early thirties' who have withdrawn from the world to stay at home and game and be basically incels. and that's not just their own stupid privileged fault, I believe, and their life is shit. I regularly wonder which one might commit suicide. That's not good!

I guess my point, peppered with perhaps incindiary or distracting stuff, is that it truly shocked me that the reaction to some particular group expressing their particular problems, and finally having an audience, whether #metoo or BLM, was met by such a virulent counter-attack. I think that's not right, and I think pointing out how that in itself means something is important.

To pull this into what seems to be the outrage of the day on HN: I think much of this whole 'cancel culture' thing is stupid, I think a lot of it is virtue signalling, and I agree with many here who describe it as such.

but I am a bit more worried about the backlash to it than I am about the disingenuous hyper-social-media people flaming it. I'm more worried by how when I click on the profile of the outraged, they show a pattern of outrage at anything that has a whiff of 'sjw'.

I'll join them in their worry when the US president is a 'sjw' and not very much in their camp. I mean, jesus fucking christ it's not like these Twitter woke people have power that truly compares to that of the president and his cronies, and it's not like a fired SV not-woke-enough dude won't find a ridiculously well-paying job somewhere else.

I'm about to but trying not to go off on the "oh but the real problem is polarization" (self-proclaimed centrist) crowd, which in our current climate strikes me as akin (but no, not quite the same) as someone arguing that perhaps we shouldn't be so mean to Hitler because his anti-semitism is just a political game. or someone arguing that somehow a US mainstream democrat is anything but right-of-center by most measures.

Well okay I did anyways and while I'd prefer no responses to this so the ramble can just be something I've wanted to ramble about and I'm not reminded of how I didn't make a concise or proper argument, here it is anyways because it feels like there might be something in there that's worth not just pasting in my personal journal like I usually do. Feel free to disregard the focal point(s) and ant-fuck the details though, that's fair game. I love y'all here and if nothing else I'll agree that being able to converse about things is well worth protecting!

EDIT: ugh holy shit is this longer than it looked in the <textarea>. if you actually read the whole thing my apologies and please keep in mind I was rambling and this does no represent my well-considered views. also, go read better stuff! if you just scrolled down to this part, keep scrolling. I said some stuff and it's probably sort of okay, by my estimation, but too long to be worth what you'd get out of it. scroll on maybe.