Sexism is not about woman. When we call a country "she" we are making a female description of what a country is: nurturing her citizens. And since there are more and more single fathers we should be allowed to call a nation "he" instead of "she".
I often write in HN with the phrase "but your average uncle joe..." and this is sexist. So one day I will be asked to write "your average auntie Mary" or better yet "your average consumer."
Freedom of press should be honored. If I were an author and I like to write with "he" instead of "they" I should have that freedom. Yes, the project is owned by contributors. So like I said, let other contributors rule him out.
And why do we have sexism in the first place? Because we all assume to have some roles in this society. Today women want the same rights that men do, but there are also rights that men don't get easily (or assume to have less). For example, raping a woman is a big crime but raping a man, have you ever heard of that? Sure. But to some people that's less severe than raping a woman. I am just stating the obvious. In some countries, raping a man is a less severe crime. And law is making a sexist decision.
I believe in people's performance over gender.
All points from either side will draw to the same root cause: we want to be superior. We want to demonstrate that we are superior. We don't really want to be equal, we just want to be superior. If you think about it a moment - that's really where sexism lies. Because there are fewer woman in engineering, we ought to demonstrate our success and ability too.
I have bias, yes, because I am a man. Who doesn't? But I see performance. My sister is very capable and more capable than I am. I always look up to her.
And yes, the solution is to make gender neutral but we are looping between anti-sexist and feminism. There is often a confusion between what a feminist, a sexist or an anti-sexist person would do... We need Yi-Yang logo here.
-- EDIT --
I just thought this is a legitimate question to ask: any difference between an anti-sexist and a feminist? Do feminists prefer gender neutral or do they prefer to have "she" instead?
What we have learnt is that the CEO of Joyent is prone to over-reacting and will fire people over nothing. So don't work for Joyent as there is no job security when you can be fired for a commit.
If you're a Joyent employee and you're not part of the Node.js groupie love-fest, better spend your holiday looking for a new job. Imagine a lunch-time conversation over the Affordable Care Act, would you dare voice your opinion?
To Bryan Cantrill, just because you're the boss doesn't mean you can fire at will, without cause, and ruin a programmer's life, unless that is you like the idea of a lawsuit and getting into the press since literally nobody is talking about Joyent and SmartOS anymore.
Ben's dismissive attitude, and yours, is exactly the issue tech-communities needs to tackle & extinguish. No, sed 's/him/them/' isn't going to suddenly make the world a better place but it's the thought that counts. Every small step counts. Ben's attitude about it, just closing the PR and claiming not to be concerned with trivial matters is something that at least needed a serious HR sensitivity discussion. Firing Ben for it is extreme, but not unreasonable if a company wanted to send a pro-diversity message; albeit extreme. These kinds of actions also provide a good filter for future employees. If you're so bothered by Joyent's blog post that you won't work there and you tell others to quit, it's probably better for Joyent not to have you as an employee to begin with.
+1 on that PR and on Joyent's blog post.
EDIT: Stories about sexism & racism, minor or major, in the tech-scene almost always disappear off HN's front page in like 2 minutes. That's another symptom of a problem as far as I'm concerned.
It's completely unreasonable to fire someone over what in essence is reversing a commit. It might warrant a discussion with a manager, it might warrant an official warning, and perhaps some other measure but summary dismissal? No way.
In my opinion, this is Bryan backing Isaacs, perhaps in a clash of egos with Ben, and grand-standing over an issue which he believes will earn Joyent brownie points.
I don't want any developer to work in an environment where the CEO openly boasts about firing people, so in summary, I guess, fuck Joyent.
>> What we have learnt is that the CEO of Joyent is prone to over-reacting and will fire people over nothing.
If you think what took place in that github thread was nothing, you represent exactly the dismissive attitude of sexism the tech-industry needs to get rid of.
A good CEO would ask the relevant manager to sit the two parties down and resolve the situation. If it were not possible, human resources could be brought in to assess the situation and perhaps administer training and/or disciplinary action. A sign of a bad CEO is knee-jerk firing and to write a blog post, boasting about such a hypothetical firing, shows incredibly poor judgement.
Let us imagine though that Bryan was right. So why doesn't Bryan fire Isaacs too? Isaacs broke commit rules by not getting his patch signed... what if this was some other commit which made it into deployment and brought down services for paying customers? Shouldn't Bryan view Isaacs as a bad employee who disregards rules and is thus a dangerous liability to the company?
"@isaacs may have his commit bit but that does not mean he is at liberty to land patches at will. All patches have to be signed off by either me or Bert. Isaac, consider yourself chided." https://github.com/joyent/libuv/commit/804d40ee14dc0f82c482d...
The person who committed the offense is the person who should be held responsible. this isn't a matter of opinion or a "cat fight" and your response is exactly why things aren't changing in tech. Most women have encountered a sexist at some point or another, tried to get it fixed and been told to "work it out." How exactly do you "work it out" with someone who is fundamentally convinced your issues are irrelevant?
Oh no, quite the contrary, I'm afraid. They constantly attract large discussions and pointless drama that always gets nowhere. As we are observing right now.
What happened: a maintainer refuses a pull request changing a pronoun in a doc on the grounds of "triviality", without giving more context. Joyent at this stage had two options:
a) reach out to him to stress why they thought it was actually really, really important, or at least get his deeper reasons b) act as if somebody peed in their coffee and write an angry blog post talking about firing people, because Open Source doesn't have enough drama already - it's just missing some more good keywords like Pulseaudio to trigger the best flamewars
It's fascinating to see how supposedly smart people behave with the emotional maturity of a toddler.
Anyway, as of a couple of hours ago, Ben posted this comment on the Github issue:
Hi all, let me try to clear up a few things.
Why I rejected the pull request. Us maintainers tend to reject tiny doc changes because they're often more trouble than they're worth. You have to collect and check the CLA, it makes git blame less effective, etc.
That's why the usual approach to such pull requests is 'no, unless' - in this case the 'unless' should probably have applied. To me as a non-native speaker, the difference between 'him' and 'them' seems academic but hey, if it gets us scores of female contributors, who am I to object?
Why I reverted the commit. In hindsight, I should have given Isaac the benefit of the doubt because I don't doubt that he acted with the best of intentions. On the other hand, if another committer jumped the line like that, I would have done the same thing. We have procedures in place and no one is exempt from them.
To the people that felt it necessary to call me a misogynist: I volunteer in a mentorship program that gets young people - especially young women - involved in technology. How many of you go out and actively try to increase the number of women in the field?
I'm probably going to step back from libuv and node.js core development. I do it more out a sense of duty than anything else. If this is what I have to deal with, then I'd just as rather do something else. Hope that clears things up. Thanks.
Well, thanks Joyent. Hope the extra publicity was worth it.
If we do let Ben be a good man as he claims to be, then maybe it was a stupidity to rule out the ticket so quickly. How would a clever "sexist" person do? This "sexist" person would probably say "well, I don't like they. Not the way my teacher taught me grammar. Rephrase the whole sentence."
Or just don't bother deal with any pull request related to sexist.
But I agree with the parent. The CEO is afraid of any negativity. This is a typical way people handle crisis - find someone responsible and fire that person. A true heroic responsible CEO should first accept / address issue with the PR, then if the community thinks "YES DO IT" then accept the pull request and requires at least 2 contributors with sign off privilege to accept a pull request from that point onward. Firing someone quickly is the worst way to be a boss.
That is for anything 'controversial' There was a post the other day that found it was any story that has more comments than likes, and atleast 40 comments will be penalized. So, if you want stories like this to last on the front page longer do not comment on them as much.
As for your rape anecdote... I hope you'll give the mechanics of that a bit more thought? And also consider the type of physical injury. (Many rape victims suffer damage to their internal organs and/or lose the ability to conceive.)
If the standards of language are changing, then we have to decide what punishment, if any, we deal out to those who don't keep up quickly enough.
http://www.washingtonpost.com/politics/justice-dept-expands-...
Think before you react.
Comments like,"Don't drop the soap," are so benign in our culture that you would have to be in a hypersensitized environment to be concerned about repercussions of any sort.
How many people feel as if justice is served when a male prisoner is raped to death, à la Jeffrey Dahmer. In fact, many would not call Dahmer's homicide a rape, but switching genders would absolutely qualify it as such.
I'm sounding as if I'm on a soapbox about this, but I'm not defending female rape in any way or the power imbalance of gender in most of the world.
Feminism is about equal rights, don't worry.
"Most women in the United States do not even know or use the terms colonialism and neocolonialism." I found this statement to be emblematic of the issues this book has, it is right around 125 pages of assertions and 0 pages of proof, data, reasoning, or any sort of factual grounding beyond the implicit goals of the author.
"Future feminist studies will document all the ways anti-sexist male parenting enhances the lives of children" This is a second thing the book frequently proposes, while feminism doesn't have an answer today, we're sure we'll have an answer tomorrow.
The book itself had a deceptive title, it should be titled "Feminism is for marxists who claim to have all the answers but hand wave giving any".
This is an example of gender stereotyping.
Though does this have anything to do with culture? I honestly don't know. I use that as an example to ask myself whether sexism is conditional or not. You can use "it" or "she" to refer to a country (or a land if you enjoy poem hahaha), but I supposed most people will not find that sexist. So sexism is condition and has to do with the story (the context in which the pronoun is used).
That means he does care. He cares enough to enforce gendered pronouns in the face of others who prefer neutral pronouns.
For a possible answer to this (admittedly rhetorical) question, please re-read my comment, particularly the lines "...doesn't want to encourage this kind of contribution to the project."
Some developers cleverly attach their name to famous project "Contributors" lists by making small grammar changes to the documentation, and then put it on their CV. In my mind, that's actually not a bad thing, since documentation is improved and everyone benefits. But I can understand that some developers may not think that such recognition is deserved.
He may have reverted because it might have appeared that Isaac was trying to bullishly overrule him in violation of project guidelines (I'm not sure whether that's actually true, but it may have appeared as such).
People who improve the code or documentation, even if it's in some really minor way you don't care about, are vital to any open source project. If you exclude them, you're voting for your project to remain small and irrelevant.
This is a blog post. Taking away a man's livelihood by firing them is widely accepted as perfectly normal and reasonable, and hn posters regularly talk about how they wouldn't want certain people working for them.
You're making a tone argument about calling someone a vulgar name, as if that is somehow worse or more important than them insisting on contributing to the pervasive exclusionary effect of gendered language.
First, let me get it out of the way that I actually agree with the pull request. In this day, the personal pronoun "they" makes a more inclusive pronoun that just "him". Zed Shaw's suggestion of "you" is also a good alternative, particularly if you're wanting to be less formal.
That said, let me note that many of us were taught in school that using "he" here is the preferred pronoun. And that's just one reason why I can imagine why someone would reject this pull request. Because as much as I agree with the PR, I have the ability to conceive of other perspectives. We have no idea why Ben chose to reject the request.
1. Maybe he thought it was incorrect grammar. I disagree, since there's a strong history of singular, third-person use of "they" in English. But it's what we were taught.
2. Maybe he's overwhelmed with issues and pull requests, and thinks this is too trivial of a matter and doesn't want to encourage this kind of contribution to the project.
3. I can think of about 3-4 other valid reasons, but I won't bore you.
Bottom line, this has all the characteristics of a witch hunt. Joyent is OK with taking away a man's livelihood because he chose not to accept a two-word commit, and one that didn't even deal with code? Not only that, but to publically call him an asshole?
I'm all for making small steps toward gender equality like this one, but calling someone who doesn't share that opinion vulgar names and wanting to fire them is an altogether inappropriate move.