> Here's hoping Ben now finds a workplace that appreciates him for his talents and respects him as a person.
He'd better find one that respects him more than he appears to respect women.
What's oddest about this is the amazing volte-face Bryan Cantrill appears to have performed. It wasn't that long ago he was adressing gross deficiencies in Solaris' performance compared to Linux on SPARC hardware with snarky, personal, and rather sexist jokes: http://www.cryptnet.net/mirrors/texts/kissedagirl.html
(On edit: added more about Cantrill's own background in this area...)
"He'd better find one that respects him more than he appears to respect women."
I've read his responses twice now, and i don't see, in either case, anything that makes me think he doesn't respect women.
Can you please point it out? I'm genuinely interested. The guy said like 7 sentences none of which said anything like "i think what is being done here is wrong" (instead, he said "i generally reject trivial doc fixes for X reasons") and is being crucified.
From where I sit, you have to add a lot of implications and subtext to what he said to get anything like that.
IE Do you not take him at his word for why he rejected the changes?
Or do you believe the very act of not being interested in these types of trivial doc fixes, when some of them change gender pronouns, makes him disrespectful of women?
(I've belonged to plenty of open source projects that would reject trivial comment/doc fixes like this when done en-masse, regardless of whether they were to fix spelling or gender pronouns or whatever, so i'm willing to take him at his word)
That's it?
That's the reason to crucify someone?
That seems insanely short sighted and stupid.
Without inserting any personal views here, crucifying people who appear completely ignorant of a cause, or don't understand the level of concern you feel about something, is not an effective method of advocacy.
It's exactly the opposite.
If you don't understand how to be an effective advocate, you tend to hurt rather than help your cause.
Well, for a person who doesn't consider the fix "trivial", it's kind of easy to see some other (more sinister) motives behind the rejection of the fix. And then even more suspicious motives behind the act of labelling a clearly non-trivial fix as "trivial".
In my opinion, both sides of the debate overreacted, but I am just trying to explain you the viewpoint that apparently feels quite alien to you. Well, if you don't even want to understand that way of thinking, that's fine, too.
"In my opinion, both sides of the debate overreacted, but I am just trying to explain you the viewpoint that apparently feels quite alien to you."
Sure, but your description seems to kinda imply that everyone assumes everyone else are passive aggressive assholes :P. Maybe that's the case here, but i would hope not in general :)
Here [1] is a wonderful (rather long) essay on whether balrogs have wings in Tolkien's books, or not. The point of the essay is that if your prior belief is that balrogs have/don't have wings, it's very easy to interpret the evidence (whatever Tolkien wrote concerning balrogs) in a light that supports your original stand.
So in the same manner, if you don't consider the fix trivial, then everything else Ben did afterwards, seems quite suspicious really. Or if you do consider the fix trivial, then everything than ensued, seems seriously out of proportion.
I don't think he appears to really disrespect women. I would say that he is, as are most guys in tech, ignorant of issues around sexism and arrogant enough to believe that if he is not aware of an issue it does not exist. Having read his responses, I think he seems like a reasonable guy who could stand to understand the world better.
edit: it wasn't that long ago? 16 years ago I was in elementary school. That's like 3 tech aeons ago.
I think we're allowed to be ignorant of the politically correct gender issues surrounding grammatical usage in a codebase. To do otherwise is to bikeshed. On the internet no one knows you're a dog. 99% of the time I have no idea if the person I'm talking to on Github is a man, woman or has a different gender identity, nor do I care. It'd simply doesn't matter. [0]
All that original commit did is set off a giant clusterfuck of nerd rage and bikeshedding. No one should ever submit a commit like that. If you want to edit executable code and make those pronoun changes in productive commits, fine. But to make those changes to the pronouns of comments and nothing else is pure unadulterated bikeshedding and shouldn't be in any project.
This isn't about political correctness. It's about a practical consideration of the impact of language usage supported both by anecdotes from community members and academic studies. The defining quality of the "color of the bikeshed" discussion is that it makes no practical difference — but there is a difference here. When you say "bikeshedding," what you really seem to mean is "something I don't feel the impact of."
You should consider that just because something isn't important to you doesn't mean it isn't important to someone. A commit like that doesn't measurably hurt you or me, so even if it only helps someone else moderately and in a way we don't entirely understand, it is still net-good. This isn't political correctness; it's objective practicality.
Likewise... you should consider that just because something is important to you doesn't mean it has to be important to someone else. It does go both ways.
I do consider that. I am baffled that people are willing to go to the mattresses over something that they don't object to, but which they argue is unimportant to them. That they spend time arguing not 'this is something I think is bad' but 'how dare you spend time on this thing I find unimportant!'
I believe people are going to the mattresses over the rage being directed at him. They are arguing more "how dare you be so enraged at him simply for not finding the issue as important as you do!" This is why I said what I said.
Hm, that's true for a significant amount of the argument since the Joyent blog post, and that's a fair argument. But in my judgment another significant part, and most of the noise in the original commit thread before Ben even reverted the commit, is about the change itself, and featured a lot of 'why are you even touching this, this isn't important, go and teach high school girls to code if you care so much'.
Indeed, and I am not asking malandrew to act like this is important to him. My point is that we should not oppose it, not that you personally need to take action of some sort.
In other words, I'm fine if you don't want to go through and revise your docs to be more gender-neutral — it would be nice, but you should spend your time on what's near and dear to you. But to say that such a change "shouldn't be in any project" is a very different thing. It has practical benefits, even if they don't personally affect you, so opposing it is purely harmful.
I totally respect that this is an issue that is important to people. I'm not opposed to these changes in the docs. I'm opposed to these being the only changes in the pull requests. You want to crusade on this agenda? Earn it. Submit a non-trivial pull request with a bugfix or feature and bundle these changes that matter to you in with them.
This is a perfect example of a group being it's own worst enemy. Alex Gaynor is not the group. The community is the group. If this matters to Alex then he should have bundled it with something that matters to the community like a pull request with changes of utility like a bugfix or feature.
If and only if Alex had contributed something of universal value to the community in the pull request and was still called out by people for that comment change in the pull request would he actually be correct in his accusation of misogyny and gender discrimination. Instead he led an unjustified lynch mob against someone who has contributed far more than him to libuv.
I'm staunchly opposed to the use of pull requests as a soapbox and unjustly crucifying someone who did not deserve it, and judging by the upvotes, I know I'm not alone in this opposition and support of an unjustly persecuted person.
This attitude is silly. Lots of volunteer contributors start out making trivial changes because they're trivial. We take lots of trivial documentation and comment fixes at Mozilla as people's first patches. They help contributors learn how the contribution process works, such as the ins and outs of posting patches, navigating the bug tracker, etc. Rejecting trivial changes because the contributor hasn't "earned it" is a great way to raise the barrier to entry on your project. (Also, bundling unrelated changes seems like a terrible practice to promote. We like to have separate issues addressed separately.)
If the doc change is trivial, yes. If it's a significant change in the meaning of the text and how it relates to the code it accompanies, then it should be a separate pull request.
A good litmus test is, "Is there value to the community in having this as a separate pull request when someone is browsing the commit history?"
In other words, if this only matters to me and is part of my own crusade (but one that the larger community is likely to actively object to), then I should keep it to myself.
The change in question here could have been part of a larger commit of changes to documentation and comments, where the overwhelming majority of changes would be considered valuable by the majority of the community.
My point is that we should not oppose it, not that you personally need to take action of some sort.
Hmm... but isn't a lot of the rage toward Ben because he didn't take action on something that some people feel is a big deal while others feel it is not such a big deal?
I don't think so. People are mad at Ben because he reverted Isaac's commit and they thought it was because he had an ideological axe to grind. They think that Ben wasn't indifferent on this matter.
Then they should take great comfort that Ben reversed it based on his thought that proper procedure was not followed. Awesome! We can all calm down now and... oh wait... seems we still have rage. shucks.
Everyone is allowed to be ignorant, the problem is people who are not ignorant but simply dismiss issues as "unimportant" because they are unaffected. It is not the original committers fault that you and so many other people don't care about (or in some cases object to) gender neutral language, and bikeshedding is best stopped not by leaving the bikeshed unpainted but by you and others who fjnd it unimportant shutting up and not objecting to the damn color if you don't care about it. Be the reduction in trivial arguments you want to see in the world.
I'm not bikeshedding on the topic of gender. I couldn't care less about that topic. That's not my battle[0], which is why I keep focusing on other aspects of all this that are important to libuv and open-source. I'm defending an unjustly persecuted person of great value to the community and the antisocial open source behavior of using pull requests as a soap box. If debating those two issues are bikeshedding, then I'm happy to bikeshed about them.
[0] but people seem to think it is and that I'm opposed. I don't know what I've said to contribute to that illusion.
I think we're allowed to be ignorant of the politically correct gender issues surrounding grammatical usage in a codebase. To do otherwise is to bikeshed
I read this (from your grandparent comment) as meaning 'discussion of gender/grammatical issues is bikeshedding' - and that to me sounds like you think it shouldn't happen because you don't care about it, which is effectively opposing the idea. If that's not what you meant, I'm sorry for the misinterpretation.
I am speaking English as a second language, and my native language does not have gendered pronouns, and the gendered pronouns bother me every day, I cannot make myself blind to them.
Then again, if his native tongue also has gendered pronouns (as it appears to do), he should be aware of the issue, not because of English, but because of his native language has the same issue. Well, perhaps his native language user community has not yet started the same discussion, though.
You have to admit, that responding to a very informative message comparing and contracting Solaris's networking stack with Linux's with
Have you ever kissed a girl?
- Bryan
is incredibly tasteless.
But of course that was long ago.
I don't think it at all appropriate to criticize what was clearly an honest mistake with a call for his employer to fire him. I would expect that of the masses on Twitter and commenting on the PR, but not of Joyent or Cantrill.
He'd better find one that respects him more than he appears to respect women.
What's oddest about this is the amazing volte-face Bryan Cantrill appears to have performed. It wasn't that long ago he was adressing gross deficiencies in Solaris' performance compared to Linux on SPARC hardware with snarky, personal, and rather sexist jokes: http://www.cryptnet.net/mirrors/texts/kissedagirl.html
(On edit: added more about Cantrill's own background in this area...)