text:
Why Hackers Must Eject the SJWs
The hacker culture, and STEM in general, are under ideological attack. Recently I blogged a safety warning that according to a source I consider reliable, a "women in tech" pressure group has made multiple efforts to set Linus Torvalds up for a sexual assault accusation. I interpreted this as an attempt to beat the hacker culture into political pliability, and advised anyone in a leadership position to beware of similar attempts.
Now comes Roberto Rosario of the Django Software Foundation. Django is a web development framework that is a flourishing and well-respected part of the ecology around the of the Python language. On October 29th 2015 he reported that someone posting as 'djangoconcardiff' opened an issue against pull request #176 on 'awesome-django', addressing it to Rosario. This was the first paragraph.
great project!! I have one observation and a suggestion. I noticed that you have rejected some pull requests to add some good django libraries and that the people submitting thsoe pull requests are POCs (People of Colour). As a suggestion I recommend adopting the Contributor Code of Conduct (http://contributor-covenant.org) to ensure everyone's contributions are accepted regarless [sic] of their sex, sexual orientation, skin color, religion, height, place of origin, etc. etc. etc. As a white straight male and lead of this trending repository, your adoption of this Code of Conduct will send a loud and clear message that inclusion is a primary objective of the Django community and of the software development community in general. D.
Conversation on that issue is preserved in the Twitter link above, but the issue itself in GitHub has apparently been deleted in its totality. Normally, only GitHub staff can do this. A copy is preserved here.
It is unknown who was speaking as 'djangoconcardiff', and that login has now been deleted, like the GitHub issue. (DjangoCon Europe 2015 was this past May/June in Cardiff.)
The slippery, Newspeak-like quality of djangoconcardiff's "suggestion" makes it hard to pin down from the text itself whether he/she is merely stumping for inclusiveness or insinuating that rejection of pull requests by "persons of color" is itself evidence of racism and thoughtcrime.
But, if you think you're reading that 'djangoconcardiff' considers acceptance of pull requests putatively from "persons of color" to be politically mandatory, a look at the Contributor Covenant he/she advocates will do nothing to dissuade you. Paragraph 2 denounces the "pervasive cult of meritocracy". [Update: The explicit language has since been removed. The intention rather obviously remains]
It is clear that djangoconcardiff and the author of the Covenant (self-described transgender feminist Coraline Ada Ehmke) want to replace the "cult of meritocracy" with something else. And equally clear that what they want to replace it with is racial and sexual identity politics.
Rosario tagged his Twitter report "Social Justice in action!" He knows who these people are: SJWs, "Social Justice Warriors". And, unless you have been living under a rock, so do you. These are the people – the political and doctrinal tendency, united if in no other way by an elaborate shared jargon and a seething hatred of djangoconcardiff's "white straight male", who recently hounded Nobel laureate Tim Hunt out of his job with a fraudulent accusation of sexist remarks.
I'm not going to analyze SJW ideology here except to point out, again, why the hacker culture must consider anyone who holds it an enemy. This is because we must be a cult of meritocracy. We must constantly demand merit – performance, intelligence, dedication, and technical excellence – of ourselves and each other.
Now that the Internet – the hacker culture's creation! – is everywhere, and civilization is increasingly software-dependent, we have a duty, the duty I wrote about in Holding Up The Sky. The invisible gears have to turn. The shared software infrastructure of civilization has to work, or economies will seize up and people will die. And for large sections of that infrastructure, it's on us – us! – to keep it working. Because nobody else is going to step up.
We dare not give less than our best. If we fall away from meritocracy – if we allow the SJWs to remake us as they wish, into a hell-pit of competitive grievance-mongering and political favoritism for the designated victim group of the week – we will betray not only what is best in our own traditions but the entire civilization that we serve.
This isn't about women in tech, or minorities in tech, or gays in tech. The hacker culture's norm about inclusion is clear: anybody who can pull the freight is welcome, and twitching about things like skin color or shape of genitalia or what thing you like to stick into what thing is beyond wrong into silly. This is about whether we will allow "diversity" issues to be used as wedges to fracture our community, degrade the quality of our work, and draw us away from our duty.
When hackers fail our own standards of meritocracy, as we sometimes do, it's up to us to fix it from within our own tradition: judge by the work alone, you are what you do, shut up and show us the code. A movement whose favored tools include the rage mob, the dox, and faked incidents of bigotry is not morally competent to judge us or instruct us.
I have been participating in and running open-source projects for a quarter-century. In all that time I never had to know or care whether my fellow contributors were white, black, male, female, straight, gay, or from the planet Mars, only whether their code was good. The SJWs want to make me care; they want to make all of us obsess about this, to the point of having quotas and struggle sessions and what amounts to political officers threatening us if we are insufficiently "diverse".
Think I'm exaggerating? Read the whole djangoconcardiff thread. What's there is totalitarianism in miniature: ideology is everything, merit counts for nothing against the suppression of thoughtcrime, and politics is conducted by naked intimidation against any who refuse to conform. Near the end of the conversation djangoconcardiff threatens to denounce Rosario to the board of the Django Software Foundation in the confused, illiterate, vicious idiom of an orc or a stormtrooper.
It has been suggested that djangoconcardiff might be a troll emulating an SJW, and we should thus take him less seriously. The problem with this idea is that no SJW disclaimed him – more generally, that "Social Justice" has reached a sort of Poe's Law singularity at which the behavior of trolls and true believers becomes indistinguishable even to each other, and has the same emergent effects.
In the future, the hacker whose community standing the SJWs threaten could be you. The SJWs talk 'diversity' but like all totalitarians they measure success only by total ideological surrender – repeating their duckspeak, denouncing others for insufficent political correctness, loving Big Brother. Not being a straight white male won't save you either – Roberto Rosario is an Afro-Hispanic Puerto Rican.
We must cast these would-be totalitarians out – refuse to admit them on any level except by evaluating on pure technical merit whatever code patches they submit. We must refuse to let them judge us, and learn to recognize their thought-stopping jargon and kafkatraps as a clue that there is no point in arguing with them and the only sane course is to disengage. We can't fix what's broken about the SJWs; we can, and must, refuse to let them break us.
(Roberto Rosario, Meredith L. Patterson, and Rick Moen assisted in the composition of this post. However, any errors are the sole responsibility of the author.)
This entry was posted in Hacker Culture, Politics by esr. Bookmark the permalink.
786 thoughts on "Why Hackers Must Eject the SJWs"
"Civil rights" has truly jumped the shark when people openly advocate that objective merit take a back seat to identity quotas.
I am now leaning toward advocating a nearly-complete dismantling of all "civil rights" offices and positions in government and education. No more affirmative action, no "Diversity Officers," no racial/gender quotas, etc. Just a few people to collect statistics and refer any real cases of discrimination etc. to the appropriate law enforcement agencies. The current system is grinding to a halt due to massive inefficiency and internal contradiction.
The screams from the left would be epic, but I think the real-world effects would be much more positive than negative. It would be the social equivalent of Ludwig Erhard ending price controls in Germany in 1948, which began the "German economic miracle," and which many also thought would be disastrous.
Harold on 2015-11-13 at 15:49:30 said:
I wonder if you've been a bit heads down on your current projects, for this has been a not so recent and ever widening problem. GitHub in particular has become a nest of SJWs—too many incidents to quickly cite, but the "retard" one is particularly alarming given their ostensible purpose—and that "meritocracy" word you like? They purged the meritocracy rug they had in their entrance. Opalgate also went much like the Roberto Rosario incident you cite, and I note he's been forced out of at least one Python group for the usual unreasons and otherwise viciously attacked, no doubt one reason he was so forceful so quickly this time.
Or what about the Mozilla Rust documentator and public face Steve Klabnik, who's proud for "no platforming" the engineer otherwise known as the "neoreactionary" Moldbug in this year's Strange Loop conference, where the latter was going to talk about his Urbit project? Klabnik open praises "anti-fascist" AKA antifa violence in Europe, and in that context was wondering what a technology antifa should do.
We indeed have a serious problem with these SJWs tearing at our modern sinews of civilization; I'm not sure what to do other than things like ruthlessly applying the program at the end of SJWs Always Lie and "no platforming" them out of their tech positions and livelihoods. I don't see any alternatives, they certainly won't leave us alone, and our livelihoods as well as this minor detail we call civilization would seem to require such a program.
reader on 2015-11-13 at 16:02:56 said:
Very well done.
There's another excellent pro-freedom piece in the Claremont student newspaper (via Instapundit):
http://pjmedia.com/instapundit/218816/
tz on 2015-11-13 at 16:03:14 said:
But the totalitarians are at places like Apple (Steve Jobs was about merit, but he's gone), Google, Microsoft.
So what if it is easily hacked, crashes, loses data, and is unusable, we have safe spaces and let anyone use any locker or restroom they want!
BTW – how many H1-Bs are not young males from India?
I'm waiting for the SJWPL so FreeBSD can adopt it.
Eugine_Nier on 2015-11-13 at 16:11:59 said:
> The hacker culture's norm about inclusion is clear: anybody who can pull the freight is welcome, and twitching about things like skin color or shape of genitalia or what thing you like to stick into what thing is beyond wrong into silly.
What about people who can pull their own weight, in the sense of coding well, but don't apply this standard to the people they bring on, i.e., SJW who can code? Should they be brought in for the sake of meritocracy, or kept out to prevent the people they bring in from causing damage?
@tz
Steve Jobs was always a totalitarian, only he was totalitarian about design rather thanvolk-marxist causes.
Jerry Stratton on 2015-11-13 at 16:19:48 said:
"anybody who can pull the freight is welcome"
Yeah, but that's racist and misogynist, as police departments, fire departments, and the military are finding out. Removing meritocracy from the world is a long-standing desire of some segments of society; I was just reading a 1980s letter from a teacher's union rep, complaining that there's no such thing as merit pay for teachers… not mentioning that it's because teacher's unions had already come out against any form of measuring results, preferring to tie pay to certifications.
+1 Danyl Strype on 2019-04-07 at 13:49:52 said:
Totally off-topic but since it came up …
> teacher's unions had already come out against any form of measuring results, preferring to tie pay to certifications.
There's a really good reason for that. Measuring the results of teaching in any sort of fair or consistent way is impossible. There are far too many variables involves, all of which are qualitative rather than quantitative, from the inherent ability of the students, to the sort of support their learning gets in the home, to the way the culture of the school supports or erodes student learning, and so on.
You don't give civil engineers merit pay on the basis of how long it's been since something they signed off on fell down. You train them thoroughly, including work placements supervised by more experienced practitioners, and make them maintain professional certification, so that stuff doesn't fall down. This is standard in education too, and unions are right to defend it.
If you put civil engineers on merit pay, rather than paying for their certification and seniority, you could bleed public infrastructure of funding, blame the engineers when stuff starts falling apart, and cut their pay. If teachers got put on merit pay, this would be an excuse to do the same with public education.
-2 David Gerard on 2015-11-13 at 16:21:43 said:
(ardent SJW here, though I wholeheartedly concede computing chops to ESR)
At this point I must ask if RMS is not a hacker. Literally the whole point of Free Software is social justice. Or for a lesser example, Matthew Garrett, who happens to be literally why your laptop runs Linux at all.
Lambert on 2015-11-13 at 16:23:08 said:
How easy would it be, as a last ditch, to fork hacker culture and infrastructure, reinstating meritocratic ideals? If SJWs pose such a detrimental effect to software quality, the effort rebuilding the necessary infrastructure will be outweighed by more competent coders. Preventing entryism into the new culture would also be in important issue.
@David Gerard
Well, RMS doesn't see to be bothered by nearly all the programers on his projects being white men.
trutherator on 2018-01-01 at 18:10:55 said:
Re-read what he actually wrote. He said people he deals with in coding projects, he has no clue nor does he care what color or gender or religious persuasion or anything else they are.
That's the whole POINT about meritocracy. But he did mention that one target of SJW slings and arrows (re: Django) was an Afro-Puerto Rican.
My guess is he wouldn't be bothered if they were 90 percent black Lesbians.
thrasymachus on 2018-09-21 at 20:49:39 said:
Probably because white men are better at coding.
@David Gerard: Even if "the whole point of Free Software is social justice," which I think is quite arguable, that does not mean that free software must adopt anything and everything that waves the banner of "social justice."
Not to mention Hayek's demolition of the entire concept of "social justice." (The TL;DR version: justice can only operate at the individual level. Once you try to apply it to groups, you destroy true, individual justice.)
Duncan Bayne on 2015-11-13 at 16:29:51 said:
I tried raising a pull request against Coraline's covenant a while ago, to clarify wording such that restrictions on speech would apply only to the context of communications within the project covered by the covenant.
My PR was rejected – it's clear from reading the thread that Coraline and her comrades wish to make participation in covenant projects dependant upon correct speech in all fora.
Judge for yourself:
https://github.com/CoralineAda/contributor_covenant/pull/74
As far as I can tell, Social Justice is about power. It's sad because there *is* a lot of irrational discrimination in tech (including agism) and the SJWs are casting a massive shadow of mistrust across genuinely benevolent attempts to address these issues.
Why do all these losers have photos of themselves as their avatars? What kind of a narcissist do you have to be to think THAT'S what other people want to look at?
m1t0s1s on 2019-03-05 at 12:30:29 said:
That's normal for blogs which use gravatar.
Why is there so much ugliness and name calling?
@Duncan Bayne: SJWs won't be against ageism until more of them get old. Now they're almost all teens-30s, so most are probably fine with a form of discrimination that happens to their major enemies, who are usually older. Mentioning ageism would complicate grabbing power from older people.
@Duncan Bayne "Judge for yourself:"
Well, since you asked so nicely… I don't think your description is a fair summary of the discussion you linked.
If there was any doubt, then read the OpalGate discussion where Coraline made that crystal clear, an instance of such speech was in fact what sparked it: https://github.com/opal/opal/issues/941
Brian Marshall on 2015-11-13 at 17:06:05 said:
What's the deal with the ~27 projects listed towards the end of the "Contributor Covenant" page? Have all these projects bought into this shit? I have checked out a few and found the contributor code of conduct. Most, but not all, of the names are links are to github.
Random832: that's a fairly charitable position, *especially* in the context of the OpalGate fiasco.
My reading of events is that:
* the covenant categories certain speech as unacceptable
* that's fine in itself (most teams have this, whether explicitly stated or not)
* Coraline and others want to extend the context in which speech is to be regulated to all fora, not just those related to the project
My reading of this is: if you want to participate in a project to which the covenant applies, you will regulate your speech in public accordingly.
How do you interpret it?
Even if you don't agree, do you at least understand that they don't really want to do away with meritocracy, but rather that they believe that the lack of representation of some groups is prima facie evidence that it's not a real meritocracy, and that "meritocracy" is just an excuse for discrimination, and that when they say things like "pervasive cult of meritocracy" they're talking about this supposed lie rather than an actual meritocracy?
Even if they're wrong, I see absolutely no evidence that it is not their sincere belief.
>Even if they're wrong, I see absolutely no evidence that it is not their sincere belief.
Go read the entire djangoconcardiff thread. That – and events like the scalping of Tim Hunt, and Shanley Kane's entire history as a public figure – fails to support this benign interpreatuon.
Even supposing it's their sincere belief, they have a pattern of behaving like vicious thugs who want to end meritocracy in the sense I describe it.
> Random832: that's a fairly charitable position, *especially* in the context of the OpalGate fiasco.
I have no context but the thread you linked.
> How do you interpret it?
I interpret it as an attempt to prevent "loopholes" like, as someone suggested, one contributor chasing another contributor to an unrelated forum in order to harass them. Maybe some of the language is overly broad, but I'd have to see an actual example of it being used the way you suggest to conclude that this is intended to be applied that way.
Really, I'm a bit baffled by the whole thing. Normally, a project's leadership wouldn't need to justify their decision to kick someone out to others (and therefore wouldn't have any need of excessively broad rules allowing them to do so, or any rules at all).
Random832: I encourage you to have a read of the OpalGate thread linked above. It provides valuable context.
Random832: What about the context of the OpalGate discussion itself that I linked to above?
Eric, you probably want to re-read the opening two paragraphs. Lots of cut-and-paste-without-edits errors there.
There is a difference between "rules" and "principles."
The people attempting this ideological purge do not recognize that difference.
I recommend that anyone who asks that that CoC be applied to an existing project be invited to clone the project, set up that CoC and start their own form. Do it politely, be very gracious about respecting their opinion and right to form their own community.
That IS the Open Source way. If someone doesn't like how a project is being run, they have access to the source code and can fork the project to match their own needs.
Also, meritocracy and identity politics are mutually exclusive. You cannot advocate both consistently and honestly.
It's annoying. As I've said I think there are many real irrational biases in tech, and there are many approaches one can take to mitigate them – that is, to approach true meritocracy more closely.
SJWs are hindering, not helping, this issue. I've seen them drive off people who I know have been very effective in challenging irrational discrimination in the past; I'm guessing as to the reasons, but one might be a reluctance to associate with people who who treat them as enemies.
"I'd have to see an actual example of it being used the way you suggest to conclude that this is intended to be applied that way."
Rules by themselves have no intention. A fundamental principle (not a rule) is that in any organization larger than six people is that any rule that can be abused will be abused. Particularly rules that leave sanctions on behavior open to interpretation and the will of the pillory.
Random832: the chasing you describe was performed by the maintainer of the covenant. It was designed specifically to enable that behavior, an example of which is OpalGate.
I can't look into this further now, but I have checked several of the 27 projects listed on the "Contributor Covenant" page and they do seem to have adopted this Code of Conduct.
@Random832: Even if they're wrong, I see absolutely no evidence that it is not their sincere belief.
I, personally, don't care what their sincere beliefs are. Actions are what matter, not beliefs. If someone is trying to get me to give up my freedom, I don't care that they sincerely believe it's for a good reason.
To the best of my knowledge, Tim Cook cares a lot more about your code or design quality than your ability to fit a diversity checkbox; he just talks about it a little more to get people to shut up.
(It helps when you're Apple and can just throw money at "getting really, really, really good people who happen to fit those checkboxes".
But the supply of such people is limited – for reasons unrelated to "the industry is all bigoted!"
So even if everyone had Apple money – without this causing an inflationary spiral in programmer/STEM/whatever salaries – you couldn't do it that way all over.)
-3 Anonymous 4982 on 2015-11-13 at 18:01:07 said:
ESR: You are gettting more and more absurd with every passing post. Has no one told you that you don't speak for hackers? That you may well have had some good stuff in the past, but that "hacker culture" has moved on, and you aren't as relevant as you may once have been?
"Meritocracy" is flawed concept. In the original essay that defined the term, it wasn't flawed; it was satire.
Anyway, I am happy to say that ESR: you don't speak for me. Moreover, your bullshit is bullshit.
I have more to say, but I've other things to do. I'll say 'em later.
ESR: you've been properly told off now; apparently you don't speak for a "hacker" who doesn't use his or her real name and thinks meritocracy is a flawed concept.
Frankly, I'd be worried if you ever did ;-)
+1 esr on 2015-11-13 at 22:22:23 said:
>ESR: you've been properly told off now; apparently you don't speak for a "hacker" who doesn't use his or her real name and thinks meritocracy is a flawed concept.
Yes, that struck me as ridiculous too.
Eric, you are defending but one front in this war. The problem you highlight is pervasive in our society, as reflected in current events on college campuses and such prior movements as Occupy Wallstreet. What is happening is analogous to a mutating and metastasizing disease. It succeeds by consuming its host, or failing that, killing it. It's not simply a battle in defense of meritocracy in hackerdom; but an existential conflict between producers and parasites.
>It's not simply a battle in defense of meritocracy in hackerdom; but an existential conflict between producers and parasites.
I'm aware of this. I'm focusing on one battlefield because that's where I can fight effectively.
Bryan Lovely on 2015-11-13 at 18:22:34 said:
" A movement whose favored tools include the rage mob, the dox, and faked incidents of bigotry is not morally competent to judge us anyone or instruct us anyone."
eas on 2015-11-13 at 18:48:01 said:
I've had run-ins with what you call "social justice warriors." I have about as much patience for their BS as I do for "engineers" and "hackers" who are convinced that they are purely rational and meritocratic (or at least more so than everyone else). Sorry, no, if you are human, you have emotions, blind spots, and irrational biases. Acting as if things were otherwise is irrational.
>Sorry, no, if you are human, you have emotions, blind spots, and irrational biases.
Of course. But a culture in which people strive to be meritocrats despite those flaws is better than a culture of rage-mobbing.
I think the bigger concern would be over SJW's that actually write good code only as a means of implanting themselves within the culture in order to subvert it.
@Justin:
"Thank you for your concern. I do not choose to follow that set of guidelines out of fear of disrupting the project. Here's a cloned repo; you are welcome to fork the project."
I'm certain that a macro could be programmed that did this automatically…
Lev Lafayette on 2015-11-13 at 19:20:13 said:
It's all very well for to claim that one should only judge only on merit.
But one must account for the reality of direct and indirect discrimination.
http://levlafayette.com/node/457
Social justice (in the aggregate sense) most certainly exists, as injustices are applied against people on group identification, as noted above. Defaming a collective identity is a reality, despite what Hayek argued.
You need your own set of vile faceless minions, or borrow Vox Day's.
Have them join the projects with codes, have half post subtle but things which might cause offense, and have the other half report them as being intolerable, so as to bury the SJW thought police too busy to do anything but evaluate grievances. E.g.
Trans acceptance: The art of eunuchs programming.
Ken on 2015-11-13 at 19:22:10 said:
> I think the bigger concern would be over SJW's that actually write good code only as a means of implanting themselves within the culture in order to subvert it.
With a tiny change you can make that sound like rms. It's irrelevant, only the code matters.
stilkil on 2015-11-13 at 20:01:56 said:
I hire technical people and I hire engineers.
I do not care what their genital arrangement might be or the colour of the skin or the intonation of their accent or what their gender identity is.
I care about whether they have the skills to do the job and the aptitude to adapt to a fluctuating technology environment. I care about whether they are a team player and have something to contribute to the team.
I currently run a team of 8 and other than english, my team cover 7 other languages the usual differences in genial arrangement. All that is incidental to the reason they have the job. The reason they have the job is that they are qualifed to do it. Thats it.
Ticviking on 2015-11-13 at 20:04:45 said:
Tz,
That is about the worst idea I have seen here.
This applies to Vox and his mob just as much as it does to the SJW pukes who insist their feels are more important than working shipped code.
Any culture left after filtering signal from the noise of a permanent flame war SJW vs G8ers will not produce much working code.
@Lev Lafayette: "Defaming a collective identity" is still the act of individuals. It's not justice to punish any group for the actions of some individuals in that group. Which is, of course, the injustice at the core of any "social justice" movement.
David Scott Williams on 2015-11-13 at 20:24:32 said:
Two text corrections?
interpreted this as an attemp to bear the hacker culture
..you meant "attempt" I assume?
Django is a web development famework
..you meant "framework" I hope ;)
+1 Dan on 2015-11-13 at 20:47:22 said:
SJWs.
Can't live with 'em.
Can't kill 'em.
Ed on 2015-11-13 at 20:56:01 said:
Part of this conflict (but not all) is due to a misunderstanding. Critics of "meritocracy" aren't criticizing the idea of judging contributions on quality. Part of what they're saying is that due to things like unconscious bias, we humans aren't always capable of making accurate judgements of merit, and we need to be conscious of those biases in order to correct for them. They're also saying that the culture of some tech projects has the effect of disproportionately turning away certain groups of people, even when their work is of equal quality.
Hypothetical example: if someone calls some code "ghetto" it sends different messages to different people. If you've never had to seriously worry about being judged by your race, you might just hear "this code is sloppy." But if you've lived your entire life under the threat of racial discrimination, you might hear "we don't like this code because of the race of the author." You might think it should be obvious you don't mean that, but it's not. Also, at best, you're saying "in this community it is normal to be ignorant of or indifferent to the racial implications of this word, and anyone who has a problem with it is not welcome here." So most of the people who criticize "meritocracy" are actually striving for a more meritocratic process by pointing out that proponents of "meritocracy" are often unknowingly contributing to an un-level playing field.
Just as in any ideology, there are some self-interested bullies who use social justice language to do harm, and I think there is a real problem among social justice advocates in not being honest enough about that. But, having read the suggested code of conduct, it seems like if applied as written, it would be just as effective at keeping those people out.
For great justice,
elplatt
+1 rogue_philologist on 2015-11-13 at 21:30:44 said:
Pretty sure SJWs are here to stay. Enjoy your "democracy"! lol
Anonymous 4982 on 2015-11-13 at 21:49:47 said:
Actually, I don't have any more to add, besides a suggestion to look up "the meritocracy myth". In short, "meritocracies" aren't, to the extent that various other factors influence how well people do. In some cases, merit is worthless, despite what people might claim.
And this is the case in software development communities, including "hacker" communities. In many cases, women (and others who aren't perceived as white men) will face a harder time. Even if their code is good, it's not accepted as good as (objectively) equally good code (from a white man).
You should be focused on "ejecting" those bigots rather than a few social justice warriors. If you want to get rid of anyone, why not get rid of those who fight against meritocracy from a racist, sexist and similar standpoint? ("Vox day", or whatever his name is, is a perfect example of someone that you really don't want on your side if you actually do believe in meritocracy regardless of gender, sexual preference, colour of skin, or similar irrelevancies.)
A good article that outlines some the issues in one related area: https://medium.com/diversify-tech/i-m-a-white-guy-in-silicon-valley-and-i-m-done-buying-the-meritocracy-myth-2cc0ef9f9b60
Lex Corvus on 2015-11-13 at 22:09:43 said:
Does anyone have any suggestions about how to push back against the Codes of Conduct that have proliferated at technical conferences? They're obviously applied asymmetrically, as talks frequently endorse "increasing diversity" and sometimes even explicitly call for having fewer white men in tech, but anyone who calls the conference organizers on their hypocrisy risks outing herself as a crimethinker.
>Of course. But a culture in wehich people strive to be meritocrats despite those flaws is better than a culture of rage-mobbing.
Some people seem to instinctively know not to let imagined perfection be the enemy of the merely very good.
+1 Rick Moen on 2015-11-13 at 22:59:38 said:
Ken Burnside wrote:
I recommend that anyone who asks that that CoC be applied to an existing project be invited to clone the project, set up that CoC and start their own form. Do it politely, be very gracious about respecting their opinion and right to form their own community. That IS the Open Source way. If someone doesn't like how a project is being run, they have access to the source code and can fork the project to match their own needs.
Perfect assessment. Eric, I would politely suggest that you promote the Gehenna of Ken Burnside's comment, and I'll tell you why:
The right to fork (w/implied access to source) is the core principle of open source. It's the bedrock, the one thing everything else is built on. People who don't believe in it, don't believe in open source, full stop. And:
Saying to a critic, who wants changes unwanted by code maintainers, 'Well, since you want us to take measures we'd rather not, but you're most welcome to fork, and we hope both projects thrive' is polite, constructive, and provides the critic exactly what he/she wants. All the critic has to do, then, is code. And everyone gets what he or she wants.
Even better, this response is completely politics-neutral and utterly fair, from any viewpoint, and appeals to anyone who agrees to open source principles, regardless of any other convictions. It can be adopted both by those thinking hacker culture is under attack and by those who don't. It requires neither manifestos nor ejecting anyone nor rhetoric of any kind. It's peaceable and requires next to no effort — just answering back the five words 'Feel free to fork, then.'
It's fair when the critics are 'SJWs'. It's fair when they're neocons. It's fair no matter what the issue is, for critics with any ideology, and for critics with none.
In addition, anyone who claims to favour diversity would be an utter hypocrite to disfavour a policy of 'letting a hundred flowers bloom and a hundred schools of thought contend'. And it would be uncharitable to suggest they would, so we certainly should not.
(No points for identifying the quotation, still famous in my youth in Hong Kong.)
Rick Moen
rick@linuxmafia.com
I find it quite telling that those who criticize meritocracy because of the flaws in its real-world examples never seem to turn those discerning eyes on their own ideals: an end to war, poverty, injustice, prejudice, and inequality. They're starry-eyed idealists who can easily see the gap between other people's ideals and real-world practice, but not the gap on their side.
Rick Moen on 2015-11-13 at 23:04:23 said:
I meant to say 'promote the Gehenna out of….'
(I blame cosmic rays.)
@Rick Moen: Perfect. The three-word answer to SJWs in open source: "Just fork it."
+1 Jeff Read on 2015-11-13 at 23:10:13 said:
Far as I'm concerned there's a vast gulf of difference between "Bay area startup ninja rockstars" and "hackers". The Bay area startup scene resembles Harvard, Yale, and other Ivy League schools in that it selects for people who resemble the already-present establishment, regardless of merit. This is often done under the rubric of "cultural fit", which often is a fig leaf for all sorts of discrimination: gender, racial, or you're-just-not-cool-like-us. I'm every tickbox of privileged you can think of: white (literally whiter than Eric), male, cishet, Christian parentage — and I can't hang with that crowd on cultural fit grounds.
> Of course. But a culture in wehich people strive to be meritocrats despite those flaws is better than a culture of rage-mobbing.
I'm reminded of an aphorism I once heard: something which can't break can't be fixed. If "striving to be meritocrats" includes denying the existence and extent of those flaws (as may or may not be true, but as these people believe is true and certainly should not be dismissed out of hand), then it's really not.
-1 bob dole on 2018-02-24 at 07:18:42 said:
yes because people BELIEVING something to be true means we should cater in every way possible to them.
> "Thank you for your concern. I do not choose to follow that set of guidelines out of fear of disrupting the project. Here's a cloned repo; you are welcome to fork the project."
I think the problem with this approach is it attempts to provide a reason for the rejection.
Patches are accepted or rejected based on technical merit, so there are usually reasons associated. Non-technical patches, like 'Please adopt this CoC," or "Please change the license terms to XYZ," don't necessarily require a reason for rejection, just like some religious sect knocking on your door and asking you to consider joining up … 'Because I don't want to," is a more than sufficient reason.
Note: I have nothing against projects adopting whatever standards, licenses or CoC they want, but treating ideological changes like software patches misses something fundamental about what is being asked.
rogue_philologist on 2015-11-14 at 00:39:01 said:
The concept of "merit" comes from power. All these people running around trying to critique merit on the basis that it favors the powerful are correct on the basic facts. And since in Christian morality we're all supposed to be equal, this is a potent argument for the vast majority of people (i.e. moralizing bozos). And the counter argument – that, for example, open source is composed of "equals" is retarded. In fact, merit is good *because* it favors the powerful.
Let's talk about something interesting, like video games. Who is playing Black Ops 3?
Troutwaxer on 2015-11-14 at 01:09:04 said:
I agree with Eric, with one important exception: I think we should get rid of ALL the assholes. SJW assholes? Gone. Racist assholes? Gone. Sexist assholes? Gone. Liberal assholes? Gone. Feminist assholes? Gone. Conservative assholes? Gone.
Or to phrase it another way, "Assholes drive away people who might learn to code well, thus preventing us from growing our meritocracy."
Secret SJW detected
> Or to phrase it another way, "Assholes drive away people who might learn to code well, thus preventing us from growing our meritocracy."
There is no single "meritocracy." You can have merit in your own domain or project, but you don't deserve shit outside of that until you earn it.
@ Ken: There is no single "meritocracy." You can have merit in your own domain or project, but you don't deserve shit outside of that until you earn it.
BFD. Your project can be a different meritocracy than my project. Hopefully we're all improving our code.
@Troutwaxer
That's exactly my point.
Rich Rostrom on 2015-11-14 at 03:36:31 said:
This is tragic. The SJW disease is metastasizing. The SJWs demand that a core developer be excluded from a project because his opinions on a completely separate topic, expressed in a completely separate milieu, might offend potential contributors to that project.
There is no actual evidence of of such offense, nor of any useful contribution to that project being rejected because of bigotry, but the SJWs demand a pre-emptive purge lest some such discrimination occur.
I wonder what the SJWs would say if this principle was exercised in other ways.
For instance, ESR has said that monotheistic religions such as Christianity or Islam are a form of insanity (IIRC; apologies if that is a misstatement). Surely that would be "unwelcoming" to any believing Christian or Moslem, and ESR must be excluded.
I can't cite an example, but I bet I could find comments on political forums denouncing American soldiers as war criminals – by people who are also FOSS developers. Such sentiments would be "unwelcoming" to any veteran contributor, so those people must be excluded.
Let's not not forget the venom routinely directed toward "Zionazis", "breeders",and "Rethuglicans".
"But it really doesn't matter whom you put upon the list,
For they'd none of 'em be missed,
They'd none of them be missed."
>For instance, ESR has said that monotheistic religions such as Christianity or Islam are a form of insanity
Monotheism is not the relevant predicate; "faith-centered" is. But they almost coincide, as polytheisms tend to be orthopractic rather than orthodox.
> The right to fork (w/implied access to source) is the core principle of open source.
But forking an open source project is a "nuclear option". It is done only (well, done successfully) only when really needed – there is network effect, and splitting community, etc.
@Jakub Narebski:
Of course. (You possibly don't know that, back in '99, I wrote one of the major more frequently cited articles about code forking in open source.) So, if the critic feels that his/her cause is of vital importance, I'm sure a little inconvenience is a small price for helping save the world. So, 'Feel free to fork, then' is in that context a polite and constructive way of saying 'no' to someone with demands you'd rather not discuss and have better things to deal with.
In passing, I'll note that classic forks are not the only option for such a person. Ken Burnside mentioned, for example, the idea of critics 'setting up their own form'. (Which I'm guessing was supposed to be 'forum'; thus the reference in the next sentence to respecting their right to form their own community.) I believe Ken's idea, here, is that if a critic or group of critics doesn't like the social conventions and tolerated speech of a project's own discussion forum, they are free to 'fork' the discussion community by setting up an alternate one.
Then, too, I'm betting that code forks over social issues will always tend to have frequent resyncs with or without much discussion of same. Watch what happens with Matthew Garrett's I-don't-like-LKML-culture fork of the Linux kernel. How much do you think he'll veer from mainline over the long run? I'm betting not far at all, with frequent veering back.
There is a noble history, e.g., rather than being annoyed at or having strife over Jörg Schilling's questionable notions of licence compatibility and passive-aggressive complaints about Linux in cdrtools, it proved smarter and more constructive to fork off cdrkit and patch out the Schillingisms.
Network effect and splitting community, yes, and people fuss and complain over that until the fever breaks and commenters remember that community members' loyalty isn't anyone else's to hoard.
TheDividualist on 2015-11-14 at 06:08:11 said:
Klabnik isn't just antifa, he is the most shameless communist I saw for a long time, and not the watered down type of communist, but the type who uses artwork clearly reminiscent to the Soviet imagery: https://twitter.com/steveklabnik to me this is roughly like the guys who think they are clever because their swastika has three arms not four.
@David Gerard I really wish RMS's name was not dragged into it. He is far more of an "older left" type who don't turn the political into the personal and largely confine their politics to anti-war, anti-corporate and pro-spending views. The main difference is attacking big targets who can defend themselves vs. swarming up on normal average guys. So in this "older left" stuff there is something more honorable and braver. There is a difference between the revolutionary who is taking on something big, no matter how misguided his views may be, and the mob who singles out and attacks normal everyday individuals. Important to remember: back around 1930 when Hitler was nowhere and there was no war, this was precisely that one thing why the world started to hate the Italian Fascists, and how the word slowly became an insult: because they were perhaps the first group to regularly attack everyday individuals and shame them (force them to drink rapeseed oil, a laxative) or beat them up. Nobody knew what their politics is, it was these _methods_ that generated their bad rep. Everybody else obeyed some sort of a honor code to attack big targets only and not each other. So there is a lesson in there, I think. David, other people know SJWs not primarily by their goals, but by their methods. This is the biggest difference.
@Anon Vox Day isn't associated with hackerdom YET, as far as I have heard, but you look like you are doing a good job convincing hackers to buy his book.
@Jeff Read I think SJWs are far more interested in the startup ninjas than actual hackers because the first are cool and the second look geekier and they are always after the easy prestige. This is a useful difference.
@ESR this time pay attention to Jeff, this is really a useful idea, one part of the your strategy could be to communicate the difference between startup ninjas and hackers. They aren't holding up the sky, they are focusing on the Snapchat type cool, fashionable, faddish projects and as that sort of thing is naturally less meritocratic and could have more of a party-bro athmosphere… hm.
@Anon https://medium.com/diversify-tech/i-m-a-white-guy-in-silicon-valley-and-i-m-done-buying-the-meritocracy-myth-2cc0ef9f9b60
The problem here with the mentioned Navy example is that it removes "tacit knowledge" from the picture, trying to base promotions on "objective" knowledge. That is one of the reasons why socialism didn't work either. If you run job interviews, and get 10 applicants, and lets say they all are white men so it is not even about that, and all have the best records but still in 2-3 cases you will get a certain "whiff" that you somehow don't want to work with that guy. There is just the lack of that personal trust. "culture fit" is a poor term because sounds like a workplace is some community. It isn't, there is a boss and employees, and it is all about you as a boss not feeling comfortable with trusting some personally, you feel like you are not going to become friends and you fear you will be yet another adversary hire where people mostly focus on pushing work on each other but taking credit etc.
The problem is that even the term and concept "asshole" got so over-politicized by SJW types that it is suspicious. To give you an example, I have heard it said a couple of times that if you oppose abortion, no matter in how reasonable and diplomatic way you express it, you are considered a woman hater, because restricting the rights of others counts as hating them. Well, this is pretty insane, because "hate" is supposed to be something you yourself feel and not others report that they feel hated by you, but anyway, a hater is pretty close to an asshole, right?
Now of course politics like that should not appear in software projects at all, but still it is so that that is very easy to distort calmly expressed, perfectly normal opinions into "hate" or "asshole", such as:
– sticking to the traditional "he" pronoun in docs to describe user behavior
– opposing any sorts of quotas
– thinking Master/slave are normal terms in technology, in device or process control
At some level it is clear that you don't want to work with asocial people, but I think the key is that you have to set up your etiquette so that it only polices tone not content.
I mean, this is the perfect opposite of the SJW resistance to tone policing. Tone is the only thing that worths policing, not content. This means, for example, academic freedom means you can research racial IQ, but you cannot put expletives into the published results because a certain professional tone or style is expected.
[RMS] is far more of an "older left" type who don't turn the political into the personal….
Tell that to the "Software Hoarders" of the mid-80s. I grant you that in style and tactics he isn't like the more recent SJW left, but he made his crusade very personal back then, which I found particularly galling when he was attacking UniPress, who had the legal license to Gosling's Emacs, which he appropriated to start Gnu Emacs.
Note I say this as someone who worked for LMI and had his support (/ I was one of the few still willing to dine with him back then) to roommate when he launched the GNU project to consultant to UniPress for their Emacs on PCs. Nothing came of RMS's appallingly unwise appropriation because two guys who owned UniPress where mensches who were allergic to lawsuits from their own experience, and stated that they believed Gnu Emacs would increase the market for their formally supported one.
guest on 2015-11-14 at 07:19:55 said:
> this is really a useful idea, one part of the your strategy could be to communicate the difference between startup ninjas and hackers. They aren't holding up the sky, they are focusing on the Snapchat type cool, fashionable, faddish projects
I think we shouldn't be dismissing the startup folks. Just because these frontend "ninjas" are not focusing on core Internet infrastructure, doesn't mean that there's no merit to what they're doing. Those "unicorn" company that are worth many million USD have to be providing a significant amount of value (yes, including Snapchat) – no matter how hard to see where that value comes from.
And they're certainly meritocratic, inasmuch as they're successfully operating in a very competitive market environment. They're going to share our values, at least to some extent.
Mountain King on 2015-11-14 at 08:53:42 said:
i think @esr is absolutely right and all projicts should haev a coad of conduct to make them more meritocratik. I liek the covanant witch say:
>>> We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.
if @esr adopt the coad of conduct for his projicts liek NTP then he will be saying I ONLY ACCEPT GOOD CODE IF U R GOOD SEND ME THE CODE i DONT CARE OTHERWISE. witch is very fare becaus no one should cair if coad come from mars or whatever we want projict to be about teh CODE AND ONLY THE CODE. If he haev no coad of conduct then bad people might be mean to teh meritpeople and they will leave.
as usual @esr is right and THANKYOU ERIC KEEP UP TEH GOOD WORK LOL
@guest – well, they're successful today. For every eBay there were a thousand Pets.coms. And for Snapchat in particular, its appeal as an app depends on an arms race against screenshot apps, one I suspect it will ultimately lose.
Huh. Possibly-interesting anecdote: I've met Coraline briefly, at a conference where she was speaking on the usual diversity topics. I looked her up after the talk; a friend of mine had recently come out as transgender and I was looking for advice on her behalf.
General impression: I found her talk disturbing (I find most privilege-framing disturbing, more for association than content), but on the personal level she was pleasant and helpful.
James M on 2015-11-14 at 11:24:13 said:
Where's the evidence? The rejected requests will still be public on GitHub – or, if they have been adminstrator erased without trace, the evidence (missing sequence numbers) will still be. It would have been the easiest thing in the world for the original complainer to refer to those requests to demonstrate what is happening, so that the rest of the community could judge for themselves why they may have been rejected.
Evidence can be open as well as code, so let's see it.
@James M: Well, there is indeed a missing sequence number. And a page capture by a 3rd party service. (archive.is) So all the evidence appears to be right there.
What's wrong with meritocracy, from the point of view of these SJW assholes?
@efraim: To be precise, I meant the requests that "djangoconcardiff" had claimed were rejected because of being submitted by POCs – of which, according to the phrasing used, there should be more than one.
@Guest: It's the culmination, even the reductio ad absurdum, of the "progressive" worldview.
For most of history, the common attitude towards the poor was that it was just the way things were (maybe especially for the local low-status ethnic group), it was God's will, they were unlucky, and/or that it was their own fault. In recent centuries, there grew to be more of an awareness of social forces like prejudice (which is a valid p.o.v., up to a point).
But now, that attitude has been taken to an absurd extreme. It's now considered rude if not oppressive to judge someone on their (somewhat) objective merits, and to expect anyone to help themselves. Instead we are told that "systems of oppression" are crucial and must change first. Which is one of the things that makes SJWs so annoying: their problems are always somebody else's fault, they're helpless before forces both massive and subtle (e.g. "microaggressions"), so they demand that other people do something to help them.
Thus you get absurdities like masked London "anarchists" demanding that the government do more. You get protests because Yale did not condemn, in advance, potential (not actually seen!) Halloween costumes that might be offensive. If police often mistreat or shoot inner-city black males, it must be entirely the fault of the police. We must not look at all the stupid and violent things done by inner-city black males which have something to do with how police often treat them. Etc.
In short, meritocracy is repellant to SJWs because it focuses on individuals and not groups. It expects changes and growth from personal effort. That takes the steam out of demands that other people change, and so deflates the core strategy of SJWs.
> Literally the whole point of Free Software is social justice.
Lol, what? Have you confused free software with your Marxist professor or something?
[SocJus] Why Hackers Must Eject the SJWs | Social Justice Warcrimes
The Nybbler on 2015-11-14 at 13:13:31 said:
There's a much more succinct reason: If we don't eject them, they will eject us.
Fortunately, as the LKML shows, ejecting them is as simple as refusing to concede to them. They'll rage, and rant, and defame, but eventually their move is to storm out saying "see how horrible you are for not welcoming a handicapped lesbian transgender woman of color like me?". And all you have to say is "goodbye".
And all you have to say is
…"bye, Felicia."
thisisntnew on 2015-11-14 at 13:29:49 said:
esr.ibiblio.org/?p=1310
They aren't a new thing.
They've had success before having opensource projects removed.
They are trying to oust Linus now.
When they do Linux will fully go the way of mozilla,
in all systemd style "glory".
Feminists always win. They've been winning since 1870.
>Or what about the Mozilla Rust documentator and public face Steve Klabnik, who's proud for "no platforming" the engineer otherwise known as the "neoreactionary" Moldbug in this year's Strange Loop conference, where the latter was going to talk about his Urbit project? Klabnik open praises "anti-fascist" AKA antifa violence in Europe, and in that context was wondering what a technology antifa should do.
There is only one solution to violence.
We all know what it is.
Nick P on 2015-11-14 at 13:58:16 said:
Good points, Eric. I'll go further to say all of us supporting free speech, free expression, and meritocracy unite against these people and smash every attempt they make at this. They so far have been good at getting crowds to back them, magazines to denounce what they hate, careers destroyed, and so on. Yet, the nonsense they speak rarely represents the opinions of Americans as a whole. Even most liberals I know are more moderate or compromise in issues SJW's hard-charge over.
So, what they are is an extremely, vocal minority of people that tries to bully (yes, bully) others to speak and act the way they want. Their methods include verbal aggression, smear campaigns, cutting off opponents money supply, and so on. So, as in any similar situation, we should collectively disregard or expose their nonsense while blocking its harmful affects and punishing it in some suitable way. Otherwise, we're just letting bullies run all over us and our freedom. Not acceptable.
Side note: Effects of giving in to SJW's ~= effects of surveillance/police state?
Wanted some opinions on a related thought. I'm all for fighting true injustices, prejudice, etc. Much SJW activity is instead of made-up harm that exists in their head which they project onto others to target them. The alleged harms vary considerably from group to group. Anyone trying not to offend any of them literally has to maintain a list of all offensive and acceptable words or behavior in their heads while assessing every word or behavior against that before acting. In my opinion, this is very much like the self-censoring, stressful effects of living in a surveillance or police state. It's unacceptable to force someone to live that way as 80-90% of their energy is wasted catering to those that will allege offense. Moreover, many of these SJW's will campaign against police-states or censorship while behaving in a way that creates the same effects. So, I think their behavior is damaging to the mind of anyone tolerating it and hypocritical given the parallels to what they often oppose in other circles. Thoughts on that comparison?
-1 Troutwaxer on 2015-11-14 at 14:00:07 said:
@ TheDividualist: The problem is that even the term and concept "asshole" got so over-politicized by SJW types that it is suspicious. To give you an example, I have heard it said a couple of times that if you oppose abortion, no matter in how reasonable and diplomatic way you express it, you are considered a woman hater, because restricting the rights of others counts as hating them. Well, this is pretty insane, because "hate" is supposed to be something you yourself feel and not others report that they feel hated by you, but anyway, a hater is pretty close to an asshole, right?
I use the word "asshole" precisely because it seem non-political to me. If anyone tries to make it political, they're being an asshole. :)
Going forward from that thought, I think there are a couple issues here for project management. First, that everyone should have an "assumption of good will" towards everyone else who works the project. In practice that means that if someone on the mailing list uses the word "niggardly" everyone should assume that the word means "miserly" (which it does, dating back to Shakespeare) and it is not meant as an assault on African Americans.
Second, it means that the person who used the word "niggardly" should be willing to apologize to an offended African American – use of the word is probably insensitive and not everyone knows what the word means – and use the word "miserly" next time. The "offender" needs to do it without accusing the black person of being racist against white people or any of the really stupid responses I've seen to that kind of critique. Everyone needs to be willing to be educated on both writing good code and on how to not offend other people on the project. Engineer your project with the best coding and architectural practices. Polish it with your social skills.
Third, it should be understood that there will be a certain amount of mutual criticism about everything from code readability to architectural decisions, and sometime people who are excited phrase things poorly, and that this is normal, and frankly folks, get over yourselves. Everyone needs to have, at least, a semi-think skin., be willing to make and accept apologies, improve their social skills and otherwise be at least semi-professional about not shitting all over the project.
Belittling trans-folk or insisting that everyone refrain from using Cis-gendered language is not acceptable in-project behavior, and if you're a project leader, maybe accusing trans-folk of being "delusional," even on another forum entirely, will probably have consequences, and if you're not willing to accept those consequences, maybe you should STFU. (And if you're an offended trans-person, don't file a bug report because the project leader is being a jerk – take it to twitter or write about it on your blog or something.)
This isn't rocket-science. But the racist asshole and the SJW asshole* both need to learn how to behave real quick or get out of the community. They're not welcome here.
* And all the other assholes.
-1 esr on 2015-11-14 at 16:54:14 said:
>Second, it means that the person who used the word "niggardly" should be willing to apologize to an offended African American
I would not apologize. His ignorance is his problem; I refuse to allow it to be mine. I would, in fact, tell him to shut the fuck up until he gets an education.
Caving to that kind of offensensitivity only invites others to engage in language policing for purposes that are neither good nor innocent. I'm not only defending my own liberty by not buckling, I'm defending the black man's liberty as well.
+1 Kevin on 2015-11-14 at 14:00:33 said:
Based on the title I wanted to hate this post, but you are absolutely spot on.
I'm still adjusting to the negative connotation associated with the phrase 'social justice', which for my whole life has been a positive thing. I also can't imagine 'meritocracy' being a negative thing either, so I'm not sure where I fit.
d5xtgr on 2015-11-14 at 14:49:06 said:
I take it you never got as far as the actual text of the covenant at http://contributor-covenant.org/version/1/3/0? It's not nearly as objectionable as the base page the OP links to; there is none of the garbage about "thoughtless use of pronouns" or "cult of meritocracy", etc. Basically, it bans attacking the other party and doxing. In particular, the prohibition on doxing is something I'd view favourably, and the personal-attack restriction is kinda meh– I can operate in an environment with or without them; I don't need them to get my point across, but I have a thick-enough skin to tolerate them being directed at me.
That's not to say I think it's a great fit for every project- adopting it for the kernel would hamstring Mr. Torvalds's management of the project, for example, and a number of others that aren't as high-profile. There's also a number of people who take bizarrely broad views of what constitutes attacks and harassment (see comments by TheDividualist, above), but the structure of the covenant is such that the project maintainer is the final arbiter of what constitutes violation of the policy.
If the covenant matches the norms you'd like to see on your project, by all means go ahead and adopt it; as far as I'm concerned, your project = your rules. To me, the most objectionable feature of the whole business is that people may interpret it as signaling agreement with the kooks, but if enough projects take a sane interpretation of its provisions, I think that stigma is likely to dissipate (and wouldn't it just tick off the crazies to have their platform hijacked, ha!). On the other hand, if you chafe at not being allowed to insult contributors, then ignore it or modify it to fit. But I don't find it particular cause for alarm as it isn't in itself particularly Orwellian and it doesn't represent a significant step in that direction- it's just a formalisation of certain community norms which are already well within the spectrum of civilised behaviour.
+1 Harold on 2015-11-14 at 14:58:20 said:
The Code of Conduct in question includes these criteria … well, as Richelieu is reputed to say, "If you give me six lines written by the hand of the most honest of men, I will find something in them which will hang him." These require but one line:
The use of sexualized language or imagery
Trolling or insulting/derogatory comments
Other unethical or unprofessional conduct
And the ambit is total, if you represent your project in any way in public, as Coraline made crystal clear in OpalGate:
This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
The "actual text", as used by these SJWs, is nothing short of totalitarian. We're way beyond anything theoretical about these "codes of conduct."
@ TheDividualist: My reply to you is in the moderation queue, probably because we both used the word "ab–tion."
Sure, any of those lines could be twisted to penalise sane behaviour, but the point is that as project maintainer you get to decide how they're interpreted (and all of them could reasonably be interpreted in a way consistent with civil community norms). The covenant has no recourse to the Most High Priestess of SJWs or Richelieu or whomever to kick you off your own project.
And if you dislike the terms even under a sane interpretation, ignore the covenant and don't adopt it in your project. Close that bug report WONTFIX, maybe with a comment summarising what would actually get you kicked from the team under your norms, and move on. But this panicking about it being totalitarian and evil is silly at best and spreading FUD at worst.
Just another PHP hacker on 2015-11-14 at 15:27:27 said:
You speak for us, esr!
kosh on 2015-11-14 at 15:29:43 said:
Until we have eliminated our unconscious biases, there can be no meritocracy.
This is only possible by the elimination of randomness in thought i.e. creativity which is the most essential force for human advance.
Thus the reason to eliminate "meritocracy" has nothing to do with anyone's social agenda and everything to do with it being an unattainable and self-defeating paradox.
You may now return to your entirely worthless discussion of labels.
Conquest's Second Law: Any organization not explicitly and constitutionally right-wing will sooner or later become left-wing.
Why? Because people with left-wing attitudes are disproportionately drawn to work inside organizations. One can see numerous examples in recent history: "mainstream" Protestant churches, labor unions, colleges and universities, scholarly and professional associations, charitable foundations – in all these areas, the full-time organization staff are overwhelmingly left-wing, much more so than the memberships. The leftists drift in, accumulate, become dominant. People with right-wing opinions feel unwelcome, stop coming in, diminish. Some leave, others retire. The leftists squeeze out the rest.
What Is To Be Done? One shouldn't try to make apolitical institutions right-wing. That would simply expand the poisoning. All I can think of is a sisyphean struggle to detect the syndrome and roll it back "by hand" (i.e. by recruiting non-leftists to do organization work and nudge leftists to retire).
The covenant has no recourse to the Most High Priestess of SJWs or Richelieu or whomever to kick you off your own project.
And if you dislike the terms even under a sane interpretation, ignore the covenant and don't adopt it in your project.
What happens when adoption of the covenant is a prerequisite for access to all the major source repositories and distro channels? What happens when membership and recognition on other projects is denied to anyone who contributes to a non-covenant project? What happens if core software APIs or architecture are altered to break or exclude non-covenant software?
@Troutwaxer: "Asshole" has certainly been politicized in exactly the way TheDividualist pointed out. To an SJW, they're the only decent ones and anyone bucking them is by definition an "asshole". This is one of their entryist tactics; they claim to be just trying to get rid of assholes and establish decent (sometimes "professional") rules of behavior. But I think you knew that.
As for the codes of conduct, there is no doubt they are intended to eject those who will not yield to Social Justice in _any_ public space from the communities they cover. The idea (as you will occasionally see them make explicit) is to eject the anti-SJ from society entirely; if you express opinions opposed to theirs you should be shunned by all. Opalgate makes this clear — the original complaint was about a developer making a remark Coraline didn't like, completely unrelated to Opal, on Twitter. The Go code of conduct makes this clear: "if your conduct outside the Go community is against our values (below), it may affect your ability to participate within our community." (The Django code of conduct, which the Go code of conduct borrows from, contains similar language.) The disinvitation of Moldbug from Strangeloop makes this clear. The ejection of the Honey Badger Brigade from the Calgary Expo makes this clear.
The idea is nothing less than to make a political litmus test for participation in open source, or any other arena they can manage to get control of.
Mousse on 2015-11-14 at 17:03:47 said:
[Whynotboth.jpg] Isn't the world big enough for meritocracies some places, and charity in others? I won't tell you how to run your life, don't tell me how to run mine (unasked). Dowhatchalike.
>Isn't the world big enough for meritocracies some places, and charity in others?
I think so. I want the SJWs to go do their "charity" thing (if that's what it is) somewhere else, and keep their slimy tentacles off my meritocracy.
@Rich Rostrom
First, I think you're arguing cross-purpose to me. I'm simply pointing out that adopting this covenant does not mean espousing the extreme political correctness these folks advocate, and its existence is not cause for alarm. Your scenarios are more addressing what happens if that extreme political correctness is espoused by major players in the FOSS community, which would in itself be cause for alarm. The covenant is purely incidental to your propositions; in them, one could as easily replace "adopting the covenant" with "having a gender-balanced core team" and the idea is the same- neither one is intrinsically objectionable or alarming, but forcing somebody else to certainly would be.
Specifically addressing your three what-ifs, I've tried to offer a variety of options depending on where you want to fall on the spectrum of idealism to pragmatism.
> What happens when adoption of the covenant is a prerequisite for access to all
> the major source repositories and distro channels?
Seeing you as the project maintainer:
(a) Refuse to adopt it, set up your own channel, and let the 'market' decide where the balance is between defending free speech and norms of civility,
(b) Adopt it and use your authority of interpretation to be as permissive as the repository-enforcer will let you get away with, or
(c) Adopt it, conclude that the behaviour it proscribes is in fact outside the bounds of social norms, and adjust your conduct accordingly.
> What happens when membership and recognition on other projects is denied
> to anyone who contributes to a non-covenant project?
Seeing you as a would-be contributor without enough influence to change either side's mind:
(a) Contribute to your non-covenant project and don't contribute to the covenant one as a form of protest against the non-covenant one,
(b) Contribute to both, using a pseudonym for one or the other so as not to trigger whatever blacklisting mechanism is employed by the covenant project, or
(c) Contribute to the covenant project and either fork the non-covenant one to apply the covenant or wait for someone else to do so.
> What happens if core software APIs or architecture are altered to break
> or exclude non-covenant software?
Seeing you as the maintainer of the affected non-covenant software:
(a) Use a replacement for the covenant software (an existing alternative or a fork you or somebody else made),
(b) Use technical means to bypass whatever exclusion mechanism or breakage the covenant package introduces, or
(c) Choose option (b) or (c) from the first answers.
I'm sure if you're reasonably creative you can come up with a solution that fits you just fine.
Why Hackers Must Eject the SJWs - Blastar Business Blog Blasts
esr: I would not apologize. His ignorance is his problem; I refuse to allow it to be mine. I would, in fact, tell him to shut the fuck up until he gets an education.
I would say, "My use of the word "niggardly" was not a great example of sensitivity. However, "niggardly" means "miserly" and has meant so at least since Shakespeare's time, long before the use of something which sounds similar to describe Black people. So I apologize for your hurt feelings, but also strongly suggest that you add the word to your vocabulary so you don't make a mistaken assumption of racism in the future."
I might even add a link to the etomology of the word "niggardly," and I would certainly judge my correspondent by how they reacted to my response. Unfortunately, "Shut the fuck up until you get an education" is why you're part of the problem rather than part of the solution. IMHO, you don't need to be infinitely tolerant of every idiot in the world (I'm certainly not) but you can certainly do better than "Shut the fuck up."
As I've said before, the failure mode of "anti-asshole" is "bigger asshole" and I wish you'd stop falling into that trap. I think you've got another revolution or two inside you, but it won't happen if you spend your time screaming that some messed up SJW needs to get off your lawn.
If you don't like their manifesto, (or their code of conduct) write a better one. You've done it before.
>If you don't like their manifesto, (or their code of conduct) write a better one. You've done it before.
Doctor Locketopus on 2015-11-14 at 17:32:02 said:
" They're starry-eyed idealists"
No, they absolutely are not. They use starry-eyed idealists as useful idiots. In other eras they'd be happily burning witches, hunting down Catholics/Protestants/Jews, lynching blacks…
on the personal level she was pleasant and helpful
Psychopaths often are.
@Troutwaxer:
Could not agree more. If you refuse to even try to be civil, misunderstandings will quickly become grudges and opportunities will be lost. My ignorance of Shakespearian English is my fault; your failure to realise that some people have a smaller vocabulary than you do is no-one's fault than yours.
More broadly, I see many people here trying to do to SJWs what SJWs are doing to others, to the abandonment of their own ideals. He who fights monsters…
@ Lambert: More broadly, I see many people here trying to do to SJWs what SJWs are doing to others, to the abandonment of their own ideals. He who fights monsters…
He who fights monsters… Exactly.
Further, when someone says, "I'm experiencing prejudice and I need to defend my territory," are they in fact experiencing prejudice, or are they an SJW? Maybe it's worth looking at the whole thing on a case-by-case basis and making a judgement about each particular case.
TRX on 2015-11-14 at 18:51:27 said:
> you can certainly do better than "Shut the fuck up."
"Shut the fuck up, you concern-trolling shitweasel?"
Belittling trans-folk or insisting that everyone refrain from using Cis-gendered language is not acceptable in-project behavior, and if you're a project leader, maybe accusing trans-folk of being "delusional," even on another forum entirely, will probably have consequences, and if you're not willing to accept those consequences, maybe you should STFU.
lol.. they are delusional? People are "assholes" for not going along with some mentally ill person's belief that they're the opposite gender? Transwomen are not real women, just ask any man. Now that you're been hammered to pieces on this forum, you're pretending to be "nice" and "reasonable" to get people back onto your side. But you don't fool me.
@ rogue_philologist: they are delusional? People are "assholes" for not going along with some mentally ill person's belief that they're the opposite gender?
I think you made an assumption and failed to read anything I wrote very carefully thereafter. I thereby banish you to the Abyss of Careless Readers!
Jeff Pugh on 2015-11-14 at 19:26:59 said:
I don't know you Eric, nor do I know your work particularly well. I do however know enough about you and your work to be saddened by this garbage.
http://i.imgur.com/fT9IREO.png
@Jeff Pugh: You'd make a stronger case if you explained why you think it's "garbage."
@Troutwaxer: "you can certainly do better than "Shut the fuck up.""
How about "It's not my job to educate you!"
>How about "It's not my job to educate you!"
"Shut the fuck up" is merited because the imputation of racism is not merely unmerited but insulting. Who the hell is this hypothetical "African American" to casually assume that I'm being racist rather than wondering if he might not have understood what he heard and, say, Googling the word "niggardly" on his phone?
>I want the SJWs to go do their "charity" thing (if that's what it is) somewhere else, and keep their slimy tentacles off my meritocracy.
Now that sounds perfectly reasonable to me. I certainly can't condone what you're alerted us to regarding Torvalds or Rosario, and I can't conceive of a "cult of meritocracy" being a bad thing, but neither can I see considering a group as the enemy as a good thing, outside of a game. Sorely mistaken, yes, but not the enemy. I too have suffered personally at such hands, but there's a lot of opportunity out there, and I move on, a little more carefully, but still.
@ Random832: How about "It's not my job to educate you!"
The most likely response to your phrasing is that someone who did not previously know the word "niggardly" would leave the project after assuming that you are a racist, so the appropriate response is to educate a little and calm the situation down, particularly if you value that person's coding ability. IMHO, your response is ideal, but not practical.
As I posted above, my preferred response would be, "My use of the word "niggardly" was not a great example of sensitivity. However, "niggardly" means "miserly" and has meant so at least since Shakespeare's time, long before the use of something which sounds similar to describe Black people. So I apologize for your hurt feelings, but also strongly suggest that you add the word to your vocabulary so you don't make a mistaken assumption of racism in the future."
flaviusb on 2015-11-14 at 20:02:54 said:
So, I feel like there is an important misconception here – what is a 'meritocracy'? Originally, the word was coined as an obvious satire, but in some groups it has been swallowed at face value with the actual meaning filed off. This appears to be what you have done. Many have done good work explaining why this version of meritocracy is the opposite of what it claims to be, and undermines what it claims to produce.
Some really simple examples, as existence proof rather than exhaustivity proof or anything (we can get into more details or the actual interesting bits of this if anyone responds to this comment):
– Erasure: Christine Peterson coined the term 'open source', but people tend to remember it as being coined by ESR. This kind of thing happens with science, with code, with politics, and it means that we should at least take seriously the idea that merit is not recognised as such.
– Lack of merit: Most of the technological infrastructure out there actually really sucks. Like, really really badly. This includes the stuff made by 'alpha geeks'. The really good stuff that I have seen has huge trouble getting adopted, or even recognised as such – just look at things like the VPRI/STEPS project, which made a complete system plus userspace plus applications in 20kloc. Actual 'success', even in hacker spaces, hinges on so many things that are *not* merit.
– Merit at what: Even looking at the 'alphas' of the OSS world, what most of the truly big names have in common is a bit of luck, some skill at self promotion, some skill at managing groups, and network effects. There are people out there who are better programmers than Linus, but Linus has an outsized impact, and outsized fame, because of these non-programming factors. Thus, focussing only on merit-as-programming-skill misses some really important stuff.
– False predestination: People's skill can change over time, people can move into areas with different levels of impact over time, people can accrue things (like the network effects of connections and fame) that change their impact over time. The more chances someone gets, the more help they get early on, the more likely they are to move from a low state to a high one, and chances and help are very unevenly distributed. This uneven distribution is often justified because 'it works', but that is false predestination – many other distributions of chances would also have 'worked', though of course different people would have risen to the top. Absent RCTs, it is very difficult to say that this is the optimal distribution of 'chances' and help, and indeed we have some evidence that it is *not*.
Anyway, I'm going to stop here before this turns into an effortpost. If you want to continue this though, I would be more than happy to.
>Many have done good work explaining why this version of meritocracy is the opposite of what it claims to be, and undermines what it claims to produce.
And they're all full of shit. If meritocracy weren't a real thing, worth striving for and worth achieving, you wouldn't have the comfortable life from which you can utter such vacuities. The innovation and wealth you take for granted was largely created by people who, by dedicating themselves to excellence and demanding the maximum of themselves and each other, got out in front of where anyone thought a human could be until they did it.
Hank Griffin on 2015-11-14 at 20:20:53 said:
@Troutwaxer,
I disagree with using 'was not a great example of sensitivity' or 'I apologize for your hurt feelings', as they constitute an acceptance of the claim that using niggardly is wrong or objectionable. I do agree on the importance of civility. I would respond with something like 'Your assumption of racism is incorrect. "niggardly" means "miserly" and has meant so at least since Shakespeare's time, long before the use of something which sounds similar to describe Black people.'
"If you refuse to even try to be civil"
Screeching "racist" at the drop of a hat is not civil, by any sane definition of that term.
'You can certainly do better than "Shut the fuck up."'
Try doing better than "raaaaaaaaaacisssssst!!!!!". Glass houses. Stones.
You just don't like it because the people you are crybullying are starting to respond with the level of civility that you deserve, i.e., none whatsoever.
flaviusb: yes, all of those issues do exist. Does that mean that it's not worth trying to identify and mitigate them, in order that we as a community can approach meritocracy as closely as possible?
Random832: I've seen the "not my job to educate you" line from a few people in this line of debate, now. Don't you think that, if you're trying to convince people of the merits of your argument, that your *sole* job is to educate people as to their errors and the merits of your position?
Imagine if I wandered in to a place doing say XP wrongly, loudly announced that fact, and then rudely refused to explain either the merits of my position or the errors of theirs. "We've done TDD this way for years, what do you think is wrong with it?" "Fuck off, it's not my job to educate you."
Consider your audience: how would that approach be received by that team? How is *your* approach being received by the hacker community here?
@TroutWaxer No, it's that you don't understand my objection to what you're saying, you shallow turd. "Careless reader" my fucking arse. I know perfectly well what you're doing: you've been roundly defeated on this forum, and now you are trying to placate your enemies with a whole lot of phony civility.
>you shallow turd. "Careless reader" my fucking arse.
Ban hammer descending now.
@TroutWaxer See, for example this:
Everyone needs to be willing to be educated on both writing good code and on how to not offend other people on the project.
Which is perfectly revealing of what you really think, deep down.
Another way of putting it: what is your *purpose* here? Are you trying to convince the regulars? Broadcasting your message to lurkers? Testing weak points in your philosophy by exposing it to debate?
Then: how does your approach achieve this?
@flaviusb Utter retard. Yes, Unix is fucking stupid, C sucks etc. But they are perfectly meritorious. Good luck figuring out why you fucking primitive. Hint: same reason toilet cleaning sucks but is perfectly meritorious. Derp some more.
Well, that went over everyone's head. The point of "It's not my job to educate you!" was that it's something that SJWs say. Sauce for goose, etc.
@ Hank Griffin: 'Your assumption of racism is incorrect. "niggardly" means "miserly" and has meant so at least since Shakespeare's time, long before the use of something which sounds similar to describe Black people.'
That works too. In fact, I think it works better than mine in some ways.
@ Duncan Bayne: I've seen the "not my job to educate you" line from a few people in this line of debate, now. Don't you think that, if you're trying to convince people of the merits of your argument, that your *sole* job is to educate people as to their errors and the merits of your position?
Half-agreed. On one hand, you're quite correct. In responding to a complaint, do you want to calm things down or make the argument worse? Do you want to give your enemies ammunition or deprive them of something to shout about? Do you want to have a tantrum because someone misunderstood something you said and got upset, or do you want to be the adult in the room?
On the other hand, I think we can all expect that anyone who joins an OSS effort should have basic social skills, and OSS leaders have no obligation to run a finishing school. If you're dealing with an outrage junkie or SJW, your efforts to educate will be in vain, so I wouldn't let the "attempt to educate" go on for too long before disengaging and (possibly) banning someone. There's work to be done.
@ Doctor Locketopus: Screeching "racist" at the drop of a hat is not civil, by any sane definition of that term.
Black people have different requirements for assessing and responding to racism than white people, and the consequences of making such a mistake are much, much higher for Black people. Do Black people make mistakes in their evaluations of racism? They definitely do and sometimes it damages their chances for success. On the other hand, one bad encounter with a serious racist can really fuck up a Black person's life, so I'm inclined to take any oversensitivity in stride, be really calm about it, and attempt to put the relationship back on a good footing.
@ esr: "Shut the fuck up" is merited because the imputation of racism is not merely unmerited but insulting. Who the hell is this hypothetical "African American" to casually assume that I'm being racist rather than wondering if he might not have understood what he heard and, say, Googling the word "niggardly" on his phone?
Maybe he read your blog entry about how the correct response to a misunderstanding about race is to scream "Shut the fuck up," and drew the wrong conclusions about you.
> yes, all of those issues do exist. Does that mean that it's not worth trying to identify and mitigate them, in order that we as a community can approach meritocracy as closely as possible?
The point of my post was that our existing, claimed meritocracy isn't, and that this is in general true of meritocracies. If meritocracy could exist, it would probably be super awesome, though there might still be some problems with the whole 'merit = value' thing for people who believe in eg intrinsic human freedoms and rights. But looking at the flaws in our existing, claimed meritocracy is step one in fixing them, regardless of anything else, and this is one thing that 'SJW's do in fact do.
> If meritocracy weren't a real thing, worth striving for and worth achieving, you wouldn't have the comfortable life from which you can utter such vacuities.
Several problems here. First, I never said that merit wasn't real, or that better was not better than worse, or whatever, though other people have made those arguments in other places – notably, I seem to recall you agreeing with Richard Gabriel here about 'Worse is Better'. I said that our existing, claimed meritocracy is not meritocratic. Secondly, I do not see that 'I have some okay stuff' implies 'nerd culture is a true meritocracy'. We can see this in the fact that Japanese megacorps are clearly not meritocratic, as they operate through a rank-seniority system, yet Japan still has wealth and comfort, and Japanese microelectronics and computer infrastructure are pretty damn good. So, 'has good stuff' does not imply 'has true meritocracy'.
Another way of looking at this is that one of the big problems with 'meritocracy' as an idea is that it causes a confusion between 'rank' and ability, and eventually rank becomes used as proof of ability; similarly, as you have done, 'what we have' gets taken as proof that this is the best we could have, flatly ignoring other, better stuff (like the VPRI/STEPS program I mentioned). Like, people end up essentially reasoning '((a ? a) ? a)', which is false.
Hmm, unicode doesn't seem to make it through this comment system.
Those question marks should render as \implies. '->' or 'therefore' is an okay substitute.
This doesn't even factor in the fact that, given that 'merit' is a complicated concept which can be cashed out a number of different ways, and whose realisation is at least partly political, if 'realised merit' -> 'rank', some people will use rank to redefine either how merit is realised, or what merit is seen to be, to keep or enhance their rank, or to stop people who they do not like from achieving rank.
+1 Random832 on 2015-11-14 at 21:42:45 said:
> Who the hell is this hypothetical "African American" to casually assume that I'm being racist rather than wondering if he might not have understood what he heard and, say, Googling the word "niggardly" on his phone?
Well, to play devil's advocate here, he might – even knowing it has an unrelated etymology – believe that your choice of such an otherwise uncommon/obscure word was a deliberate one intended to get under his skin and/or to let you snicker* at him behind his back feeling you have got away with something.
I'm not entirely convinced, for that matter, that the incidence of people choosing the word specifically to be able to point and laugh at people who haven't heard of it before is zero.
*And/or a similar word with a similar meaning but a different set of consonants.
Thomas Blankenhorn on 2015-11-14 at 21:44:27 said:
esr> I'm not going to analyze SJW ideology here except to point out, again, why the hacker culture must consider anyone who holds it an enemy. This is because we must be a cult of meritocracy. We must constantly demand merit – performance, intelligence, dedication, and technical excellence – of ourselves and each other.
I realize this is potentially an inflammatory question in your blog, but I'm curious: Have you ever discussed this point with your friend Richard Stallman, who is both a champion of social justice and a hacker of great merit in your community? Given that he cares about both sides of your dichtonomy, I would be interested to hear where he comes down on this issue on balance.
Furthermore, I think maybe even a majority of people who do know the word first heard it in the context of "here's an obscure word that sounds like n***** but is actually innocent", and I suspect that a significant percentage of the subset of those who went on to integrate it in their vocabulary did so from a place of "I can be an edgy little shit and have an excuse to laugh at any black people who doesn't know I'm totally not being racist".
I certainly wouldn't think that of you. I know you better than that. But does the hypothetical person you've offended?
If they don't know you that well, then their prior probability of you being a racist, given you've said that word, is justified as being well over 50%, whether they know what it means or not.
Terry on 2015-11-14 at 21:58:11 said:
"Django is a web development framework that is a flourishing and well-respected part of the ecology around the of the Python language" in the article has my mind's tongue tied up in knots. Sorry for being a Grammar Gestapo :)
"Black people have different requirements for assessing and responding to racism than white people"
Ah, yes. The soft bigotry of low expectations. Black people can't be expected to use common courtesy, or give others the benefit of the doubt before taking offense, or any of that white people stuff.
You're the one who's being racist here, choom.
"If they don't know you that well, then their prior probability of you being a racist, given you've said that word, is justified as being well over 50%"
Calling someone a racist without hard evidence results in a 100% probability of being an asshole.
@ Troutwaxer
I think you have the magnitude of the problem wrong. SJWs are not a few deviant malcontents that that create an annoyance in the workplace because of hypersensitivity (and hence should be corrected and educated as if they were spoiled children). Rather, they are memetically corrupted memebots that are actively spreading an infection. If unchecked (or dismissed as benign), they will metastasize until the threat is lethal and the host is dead. You are the sort of person who will not recognize the cancer until it is at Stage 4. Good luck with that.
@ Random832: Well, to play devil's advocate here, he might – even knowing it has an unrelated etymology – believe that your choice of such an otherwise uncommon/obscure word was a deliberate one intended to get under his skin and/or to let you snicker* at him behind his back feeling you have got away with something.
I never thought of that! I just saw it as an interesting misunderstanding. But I can totally imagine it happening, "Hey Tanisha, check out the niggardly amount of memory we got allocated. Hur Hur."
+1 Troutwaxer on 2015-11-14 at 22:34:53 said:
@ Doctor Locketopus: Ah, yes. The soft bigotry of low expectations. Black people can't be expected to use common courtesy, or give others the benefit of the doubt before taking offense, or any of that white people stuff.
Not my point at all, particularly the "low expectations" part. As I am white, my consequences for not recognizing and responding to white racism are very minor. The worst that could happen is a Black friend might become angry with me. The consequences for a Black person not recognizing racism might literally be life-threatening. So I set my "threshold" for noticing racism to a level which is safe for me, and my Black friend sets his "threshold" to a level that is safe for him, and we end up with wildly different responses to the same situation because the consequences for each of us is vastly different.
Also note that a Black person can win big by pointing out trivial points of racial etiquette, (by "win big" I mainly mean stop violations before they get worse,) while a white person can win big by ignoring those same violations of etiquette. The Black person is clearly in the loser's corner here, because pointing out too many violations makes him/her a killjoy, while pointing out too few violations makes him/her a doormat.
@ TomA: I think you have the magnitude of the problem wrong. SJWs are not a few deviant malcontents that that create an annoyance in the workplace because of hypersensitivity (and hence should be corrected and educated as if they were spoiled children). Rather, they are memetically corrupted memebots that are actively spreading an infection.
Agreed, but who among these three hypothetical people is an SJW, who misunderstood what you just said, and who is a truly oppressed person? They're all using college-level language to discuss the problem, and they're all angry. Figuring out which one needs to be thrown out of your organization, which one misunderstood what you said, and which one needs help and support is not a trivial problem, and you have to do it before the SJW recruits the other two into the cult!
What's pissing me off about the whole discussion is that we're treating the easier part (getting rid of the assholes) as if it was a difficult problem which requires high-level ideological cognition, and we're treating the really important and very difficult part of figuring out why people behave as they do and what we should do about it, as if it were very, very easy. This won't end well.
Alex K. on 2015-11-14 at 22:35:58 said:
@kosh:
and/or @flaviusb:
… 'merit' is a complicated concept which can be cashed out a number of different ways, and whose realisation is at least partly political, …
If,as you claim, political or unconscious forces has prevented the formation of (by your definition) a true meritocracy, how do you measure this? And more importantly, what proof can you show to convince me your measurement does not itself contain unconscious or political bias?
> If,as you claim, political or unconscious forces has prevented the formation of (by your definition) a true meritocracy, how do you measure this? And more importantly, what proof can you show to convince me your measurement does not itself contain unconscious or political bias?
@kosh: Please see the examples I listed earlier in the thread, as existence proofs. I deliberately picked simple, obvious examples – things like who gets credited as coined the term 'open source', vs who actually did. It is obvious that if, say, Christine Peterson coins a term, and then ESR generally gets the credit for it, this is an example of 'meritocracy' being not meritocratic – this is especially poignant as the term in question is 'Open Source', and the whole dialogue around Open Source is fairly key to modern nerd culture.
My claim is not that 'political or unconscious forces has prevented the formation of (by your definition) a true meritocracy', but that 'the currently existing nerd culture has these (amongst other) problems, so it isn't a true meritocracy (under its own terms)'. Politics and unconscious bias and so forth only come into the discussion later, after my claim has been shown.
Sorry, that should have been @AlexK, not @kosh.
> Ban hammer descending now.
Have you ever banned someone for being too far left, or do you only ban people for being too fat right? If so, you might want to think about what kind of selection pressure this is exerting on your commenters.
>Have you ever banned someone for being too far left, or do you only ban people for being too fat right?
I never ban on political grounds at all.
Russ Nelson on 2015-11-14 at 23:47:29 said:
Wow. I view OpalGate as nothing more or less than an attack, not on any one contributor, but on Opal itself: https://github.com/opal/opal/issues/941
"meh" clearly has nothing but contempt for the attackers, which is all they deserve.
Tim Kramer on 2015-11-14 at 23:48:18 said:
It's not just the coders. This issue impacts just about any volunteer effort. My example: I was driven out of a documentation effort by newly-arrived "experts". I was publicly scolded for using "see man page" because it reminds the "vision challenged" of their disability. I left the project, after noting that I'm legally blind in one eye and that the only thing brought to mind by such discussion was that there are asinine people in the world.
Bruce on 2015-11-14 at 23:50:01 said:
@'niggard of question, but in answer'- It's a large assumption that Shakespeare, author of Mercutio's statement that he'd sure like to butt-rape Juliet, not to mention Ophelia's country matters, was too classy for ethnic humor about funny-looking foreigners distant from him by several months dangerous travel.
@troutwaxer 'the really important and very difficult part of figuring out why people behave as they do' isn't all that difficult. Computer Science 101 attracts a lot of dumb, lazy, and ignorant people, as well it should. Like Bonehead English, it is aimed at getting those of us who are dumb, lazy, and ignorant of the subject up to some minimum adequacy. Given the large chunk of IQ 80-95 people going to subsidized college, a large chunk of students needs easy A's. Pop Sosh, Eng Lit, Computers for Dummies, all easy A's come with loyalty oaths to the Democratic Party. Four years of that, and they have the certificate they need for a sit-down job. What happens when they compete with smart people who learned their first computer language at six? They can't show Eric their code. They aren't even script kiddies. Back to flipping burgers? If education loans are enforced any more tightly they'll be back to debtor's prison.
Or semi-legal parades! With studly yelling and maybe some fistfights and vandalism! And loyalty tests: remember, they really are more loyal to the Party than Eric, and they know it. Display their loyalty to the the Democratic Party, display strong feelings of outrage, flaunt the courage to stand their ground, bark their scorn for 'meritocracy' as the oppression dreamed up by those smarty-pants triple-digit IQ work-ethic-privileged evil enemies? More fun, more effective; I'd be doing it too.
Eric's problem is keeping low-IQ Party loyalists who will always have more political clout and vastly greater numbers than his side from taking over Open Source and breaking it without ever being competent to know they've done it. Won't be easy.
@Russ Nelson: Wow. I view OpalGate as nothing more or less than an attack, not on any one contributor, but on Opal itself…
I don't know how to interpret this particular controversy because the remarks about trans people aren't in any kind of context. If anyone can retrieve the original post, which appears to be dated around June 17th on Twitter, along with its surrounding context, I'd be thrilled.
"Not my point at all, particularly the "low expectations" part. "
Yes, it was. It was exactly your point. Exactly.
"As I am white, my consequences for not recognizing and responding to white racism are very minor. The worst that could happen is a Black friend might become angry with me."
Funny, I could've sworn that two University of Missouri officials just lost their jobs for allegedly doing that.
"this is an example of 'meritocracy' being not meritocratic"
You are implying that lack of perfection in the existing system constitutues evidence that your hypothetical system is going to be better, come the eschaton.
History has shown again and again that this is not the way to bet.
Have you ever banned someone for being too far left, or do you only ban people for being too fat right?
Roger wasn't banned for being "too far right", he was banned because he's been banned repeatedly before and keeps coming back using alts and displaying the same behavior that he got banned for (specifically, the snide and gratuitously insulting tone that Eric explicitly called out right there). I'm not entirely convinced you're not an alt yourself, for that matter.
@ Doctor Locketopus: Funny, I could've sworn that two University of Missouri officials just lost their jobs for allegedly doing that.
Not a fair comparison for 99 percent of the human race. A university president is paid, – fundraising – first and foremost, – fundraising – to make sure that the school – fundraising – doesn't have a scandal which makes the papers… whatever tensions were involved should have been quieted long before they made the nightly news. We're not talking about anything here but sheer incompetence.
The consequences for a Black person not recognizing racism might literally be life-threatening.
Y-e-e-e-a-h, but how often does that happen? How many blacks have been killed by racists in the United States in the last (say) 30 years? Unless you're fudging the numbers by including people like the auto-Darwinated Michael Brown, then the total is probably less than one year in Chicago or Baltimore.
I'm not changing the subject, I'm pointing out the over-dramatization of racism by today's anti-racists. To listen to them, you'd think we were living in rural Mississippi in 1955. Or 1855. We don't have lynchings and biased poll tests any more, so people who want to get upset about racism have to freak out about trivialities like Halloween costumes and "microaggressions" and "statistical underrepresentation in movies." They act as if the KKK lurks everywhere, when it's an insignificant group that at this point is probably 75% FBI informers.
"Not a fair comparison for 99 percent of the human race."
Keep spinning, deflecting, and derailing. We've all seen your Marxism 101 rhetorical tricks a hundred times. They don't work any more.
Let's say a white person has been robbed by a black person, and suffered grave bodily harm. Does that make it okay for the white person to treat all blacks as robbers from then on, and misinterpret anything they say as part of a plan to commit robbery?
Of course it doesn't.
You are arguing that black people shouldn't be expected to (or, perhaps, can't) abide by the standards of civilized behavior. That makes you a racist. Q.E.D.
The essence of Eric's genius in raising this alarm is that the real danger is in not seeing the danger until it's too late. Once we're circling the drain, the bandwagon of despair will be overflowing, but at that point, it'll be a little late to rally the troops.
There a more than a few dead people in Paris today because it's easier to bury your head in the sand than to take a stand.
>The essence of Eric's genius in raising this alarm is that the real danger is in not seeing the danger until it's too late
Oh, I saw the danger some time ago. But it was in the "possible threat – might bear watching" category. My threat assessment began to rise during the scalping of Brendan Eich, and more rapidly as a result of shirtgate and the fraud run against Tim Hunt. But even my source's allegations about honeytrapping didn't quite have me raising the alarm yet.
Then I learned the details of the djangoconcardiff incident. That's when I realized it was time to light the hilltop fires and call the clans to war.
Are you contributing to https://github.com/rosarior/Code-of-Merit, or is this an independent effort?
They want nothing less than to completely eradicate diversity of thought from the hacker culture in the name of promoting the victim group of the week. It's now a full-blown existential threat of the first order.
@ESR @everybody I found something interesting, a correlation, maybe not substantial, but maybe it is useful information. So this Code of Conduct is apparently accepted by Rails community, and generally it seems Rails and GitHub arefairly big on this SJW stuff, we can say?
Years ago, Zed Shaw, whom I consider a trustworthy guy precisely because of his brutally honest no-punches-pulled "gonzo" style, wrote on how GitHub is apparently infested with immature teenagerish trolls who think ASCII penis jokes are funny: http://web.archive.org/web/20110716053523/http://sheddingbikes.com/posts/1306816425.html and how it is full of other kinds of twats: http://web.archive.org/web/20080103072111/http://www.zedshaw.com/rants/rails_is_a_ghetto.html and Zed is clearly no SJW nor male feminist nor nothing, just a normal type who doesn't want to put up with idiots.
Years later, the very same space, Rails/GitHub is full of SJWs crying that penis jokes and suchlike are cyberbullying microaggression against women.
Wonder if this is related?
We know well enough how one extreme tends to raise its opposite. But in this case look at how silly both extremes look, the other described aptly by Zed. But it looks a bit like an internet war between two groups of teenagers originally?
Not sure what do with this, I am just sharing it because this correlation may matter. Maybe it is just a generic Eternal September with two factions.
Also, I am not sure it is decent for me to use the web.archive to share posts Zed has pulled. Authors decisions to retract articles should probably be respected even though paper media was never able to respect it, but the machine exists and everybody can use it and I saw them linked elsewhere. But anyway @ESR if you think better not do this, and remove this comment, I won't grumble about it, I would find that an understandable decision too.
Also, I am not trying to reduce the importance of this stuff. If anything, it is HUGE – it is not just SJWs trying to take over hackers but the political "Cathederal" slowly taking over everything. I am just saying in this case perhaps it is somehow related to former, different kinds of idiocy.
@flaviusb
Try to think of it something like sports, athletics. At some level perfect fair play and fair rules don't exist, people with genetic potential and rich moms and trainer dads have a fair higher chance at sports and so on. And merit even at what, pro athletics is not even healthy, they are pushing themselves too hard for health and use doping and game the rules etc. And what is the use in even running that fast. And and and. But still sports has a meritocracy, and it means roughly the following things: by having banned the most obvious kinds of unfairness like winning by being the referees nephew, and by made success fairly objectively measurable, they push and motivate people to try really really hard. Thus the goal of meritocracy is NOT to deliver perfectly deserved rewards to everybody it. It is to push everybody to work hard, and it achieves it by a limited, never perfect sense of fair rewards.
Think of hacker meritocracy as a halfway fair system to make hackers work hard. Like the free market. Like sports. Nothing is really fair, nothing is supposed to be, but some level of fairness is necessary merely for optimal motivation.
I think there may be some sort of a fundamental difference of political philosophy here. You may be interested in somehow delivering fully merited, deserved levels of rewards to people. I am not, I am only interested in performance, if the reward system is good enough to push max performance, that is good enough. I consider actual fairness a pipe dream.
"Fair" is a social contruct. It is constructed towards maximizing performance, not to distribute every possible reward in harmony with some cosmic sense of justice that doesn't exist because there is no god and people aren't a collective god either.
James Donald on 2015-11-15 at 05:31:29 said:
> "Black people have different requirements for assessing and responding to racism than white people, and the consequences of making such a mistake are much, much higher for Black people. Do Black people make mistakes in their evaluations of racism? They definitely do and sometimes it damages their chances for success. On the other hand, one bad encounter with a serious racist can really fuck up a Black person's life, so I'm inclined to take any oversensitivity in stride, be really calm about it, and attempt to put the relationship back on a good footing."
What utter bullshit. Blacks swagger like they are aristocrats and whites are peasants, just as women in the workplace continually interrupt and talk over their bosses. They know that the cry of racism can destroy anyone they want to destroy.
How can one bad encounter with a serious racist fuck up a black person's life? White racists do not physically attack black people for being black, while black people frequently physically attack white people for being white. White people do not have the social power to destroy a black person's career, while a black person does have the social power to destroy a white person's career for trivial and frivolous reasons.
+1 James Donald on 2015-11-15 at 06:10:54 said:
The reason that the feelings of members of protected groups are so easily hurt is that it is, under an ever wider range of places and circumstances, illegal to hurt their feelings.
This absolutely guarantees that they will feel entirely genuine hurt feelings no matter how much everyone else walks around on eggshells.
@TheDividualist: Please read what I posted earlier in this thread. I enumerated some basic ways that our claimed meritocracy really wasn't, and showed that in some cases the claims of meritocracy are really acheiving the opposite of meritocracy. Claiming that this broken not meritocracy delivers the full fruits of meritocracy, in fact the maximum possible fruits of any system is obviously false, if only because we drive out people with merit who do work hard for non-merit related reasons, and we do not nuture many people who do not yet show merit to the point where they can begin to show their merit.
Finally, I am actually interested in questions of basic fairness and justice, because good is better than evil. I do not require perfection, just that if we are given some obvious ways to be better we at least give them a solid try.
The problem with fairness and justice is that it can be incredibly asocial. Work is service provided for others. Every time anyone proposes that, I don't know, group X should have a fairer chance of becoming doctors, it automatically means that being a doctor is no longer a duty or service provided for patients but just some sort of a high-status position to bask around in. More reward than service. "Uneven distribution" primes everybody to see things as some sort of a reward to get for effort and not a job to do. The only proper goal in these regards is to not lose potential talent – if someone of group X is working in a coal mine because prejudice while could be a lawyer is obvious an amount of lost output for society, and this is what matters, not the tough luck for himself.
https://en.wikipedia.org/wiki/The_Rise_of_the_Meritocracy was obviously a satire, by a guy about as much of the intellectual ruling class as possible, but only because he seemed to buy into a similar sense of divine justice. In reality, the rise of the meritocracy in 1950's Britain was simply about easing up the former aristocratic ones and replacing more upper class twats with middle class talent because they wanted more output, more efficiency, not because distributing perfect reward could anything but a secular reinvention of religion.
But looking at your examples:
– Erasure: even if true it may somewhat demotivate people from inventing terms. Whatever, not important.
– Merit at what. Project management and people skills are important. But again if the goal is not fairness but efficiency, it is a good idea to make a few really outsized rock stars like Linus. This works everywhere from basketball to CEOs. It motivates people.
– Distributing chances is a huge bullshit, don't you smell it? It looks like there is some big hierarchy and it hands people chances. This is one of the things that always bothered me about left wing thought: does the world really look like it is ran by bosses who distribute chances? In reality people don't need to get chances, they MAKE them by starting New Things.
– You are probably right in claiming that it works like everything else in the world like there are 100 people of the same acting talent, one gets a minor role in a movie and it can launch a snowball of mentoring and "getting chances" (because movie roles indeed chances given by others, actors cannot make their own movies, it is different from software) which is at some level unfair. But what else should be done, all 100 should get minor roles and nobody ever a star? Having stars is useful and it can never be fair because there is no need for too many too big ones.
The only good argument in this regard that chances are possible that generate more collective output. I believe the best method that is called the free market i.e. if some employers regularly prejudice against .e.g black employes that depresses their salaries and someone else hires them and makes a lot of money which then ends the prejudice. So this arbitrage thing. If something is unfair in the sense of bleeding talent, there is always the possibility for arbitrage.
@flaviusb:
My claim is … that 'the currently existing nerd culture has these (amongst other) problems, so it isn't a true meritocracy (under its own terms)'. Politics and unconscious bias and so forth only come into the discussion later, after my claim has been shown.
Right, I think you misunderstood me. Right now I shall accept your claim regarding the flaws in hackerdom if only "for the sake of argument" (which is really to ensure I clearly understand your argument). Merit is not given to those most desrving and is given to several who have not earned it—but what I want is not specific examples of this. If hacker culture is not a perfect meritocracy, you should be able to describe [without using examples] which qualities it lacks. Alternately, can you give me a pattern or formula to use by which I could find all such examples of the flawed qualities for myself?
I ask because without such a rule, I can only presume you do require perfection. (Your example of the misattibution of the term "Open Source" seems to me a flaw of business culture—assigning all merit to the president, and none to underlings—or Western culture as a whole, rather than of hackerdom specifically.)
@TheDividualist: Sure, once you have a computer and an internet connection and some free time and education and mentoring and access you can make a thing. Take away those things, and see how difficult it is, how much more work it takes and how much worse a result you end up with. Those are what I was referring to as 'chances', in programming. I got into programming young in part because I had a computer and an internet connection and free time and education and mentoring and access, and I am as good as I am now in part because I got those things in fairly good supply, and also because I was able to take a bunch of time off work in funemployment, and in starting my own companies to make the stuff I wanted to make. If I didn't have those chances, I would not be as good as I am today.I want to see those chances better distributed, as I see a lot of people who could have been amazing, but the chances they got were really crap, so now they are merely okay, and I see a lot of people who got chance after chance not because they had the nascent talent, but because they looked the part, or because they sounded like a nerd, so we accepted them, or becuase their parents had money, or whatever, and they are also merely okay.
Now, I am not saying that there are some kinds of bosses that hand these things out in all cases (though yes, in some cases I was literally handed chances by my boss at the time, and in some cases I was told later that they took a chance on me because 'I really looked like a programmer') – a lot of these things are given through more complicated mechanisms, whether because your parents happened to have both the money and the interest, or because you were easily accepted as part of the 'in crowd' on IRC, instead of being told curtly to RTFM, newb, when no one has even told you which FM is possibly relevant, or where you can get it to read it. Recognising that this is a thing, we can change the distributions in some cases and in some ways to be better, and we can also recognise that 'I am not water that boiled itself', that is, that we didn't get to where we are by dint of merit alone.
Part of the reason this particularly grinds my gears is that we have some people (like Linus) who are happy to argue from authority, as they believe that their authority is a perfect stand in for their merit (because meritocracy), who end up doing a lot of damage because they (for example) don't understand security at all, and their authority lets them mandate this flawed understanding as the basis for kernel security going forwards, leading to all of our devices being permafucked.
Another part of the reason this grinds my gears is people (again, we will use Linus as an example) who use their authority to keep people from getting chances, while defending their antisocial behaviour on the basis that meritocracy means that it must not be antisocial, otherwise I wouldn't have the position that I do.
Finally, with regards to the free market and arbitrage, http://economics.mit.edu/files/553 seems like a fairly good intro to why even ideal perfectly competitive free markets do not necessarily fix discrimination, and why arbitrage is not necessarily even possible here, depending on contingent factors – such as the number of prejudiced employers, and the number of prejudiced customers, the amount of prejudice, and the rate of unemployment. Even with very low numbers of very marginally prejudiced employers and customers, unemployment rates like what many advanced economies have today would result in large amounts of effective prejudice under a perfectly competitive free market. These results also speak to the state of things in other areas too – hence why I favour intervention, either socially (to make prejudice less aceptable), or in some cases through rules or laws.
@AlexK: A complete formulation of all bad qualities, or all lacking good qualities? Fine. It lacks the quality of rank being solely or primarily through merit, where if you outrank someone you also naturally outmerit them, it lacks the quality of usually recognising and rewarding merit, it lacks the quality of efficiently, naturally and fairly stewarding future merit amongst the potentially meritorious, it lacks the quality of promoting merit amongst the constituents, and it lacks the quality of rigorously promoting meritorious works over less meritorious works.
Even if you had those things though, two major problems still remain. The first is: what merits? There are many ways to look at merit, and there does not seem to be a sufficiently detailed true answer we can all agree on. For example, many people currently are arguing that 'Go' *must* be meritorious, because lots of sofware has been written in it, and Google is promoting it. The same arguments have been made for PHP (except Facebook, not Google), and C++ (lots of places, not just one big company). Yet, these languages are awful!
The second is more a problem with what follows from taking meritocracy as a ruling philosophy: what of intrinsic human value and freedom?
>The second is more a problem with what follows from taking meritocracy as a ruling philosophy: what of intrinsic human value and freedom?
Exit over voice. This is the fundamental problem with your understanding that you put voice above exit. At some level this may be the left-right thing. Libertarians like ESR understand exit over voice on a bone level, I think. The intrinsic human freedom and dignity is in the ability to secede from others, make your own thing, community, project etc. This is exit. Voice means trying to tell other people how to run their own gang. Voice over exit results in something as chaotic and inefficient as democracy or public schools supervised by parents committee or revolutions, while exit over voice represents the efficient behavior of the marketplace where you don' tell Bill Gates how to run Microsoft, you just decide to never buy their products again and they will perhaps get the message if enough people do so but even if when not there are other alternatives, and in history represents the wise guys who emigrated instead of revolting.
@TheDividualist: I get the Exit, Voice, Legitimacy thing. I just think that exit is vastly overemphasised, and voice and legitimacy are vastly underemphasised in programming discussions, especially in cases that can be seen as resource allocation or territory based, or where there is an ecosystem, or where there are disputes over externalities. For example, Linus has basically destroyed a generation of kernel hackers – how do we 'exit' from this, in a way that saves the next generation of kernel hackers? Network effects mean that if we use exit, we are then compelled to severely diminish Linus, as otherwise he will still fuck everything up. On the other hand, if we use voice, we can explain what the problem is, and maybe use persuasion and social pressure together with a micro-exit to actually fix the problem, with Linus getting to stay not diminished at all.
Also, I tend to believe that democracy is good, and that many past revolutions were necessary for us to have the good that we have today.
I don't know how to interpret [the OpalGate] controversy because the remarks about trans people aren't in any kind of context.
The context is here https://twitter.com/elia/status/611319469982527488 It was about gender reassignment surgery, including for children, e.g. "I still fail to see how that kind of invasive surgery on kids can b cherished".
You answer my question regarding a heuristic with "lacks merit", and then rather than giving me a definiton just ask an open ended question and cite examples that there are several competing definitions. If you aren't able to tell me directly what "merit" you're looking for, how can I be sure you will see it when it arises? Why should I believe you have a real vision of merit, rather than being some sort of nihilist who only wishes to degrade the works of others?
Let me second what TheDividualist said. If you feel that a project isn't being meritorious, you are fully empowered to build and promote an alternative of your own. The fact that you are arguing to impede the freedoms of others to follow their definition of merit rather than pursuing your own implies an awful lot about how much you actually believe in freedom, equality, and merit.
"Sure, once you have a computer and an internet connection and some free time and education and mentoring and access you can make a thing. "
Internet connections are free at nearly every public library, coffee shop, and McDonalds in the country. Older computers adequate to write code are free for the taking (you can even get people to pay you to take them away, if you play your cards right). Unemployed people or people on welfare have plenty of free time. Education is free on the web and at the aforementioned library. Mentoring is nice, but not necessary. I'm not sure what you mean by "access", but there plenty of public repositories to distribute your source code.
In short, your argument is bullshit.
@AlexK: I gave you the list of qualities that hacker culture lacked to be a true meritocracy, because that is what you actually asked for. You never asked me to define merit. If you had asked for a rigorous definition of merit, I would counter by asking you for something that is surely simpler, as it is a restricted form of that question: surely you can provide me with code that will unambiguously tell me which code is good and which code is bad, for all forms of code? That is, it will detect all flawed algorithms, all security problems, all memory leaks, and so forth? What is that, you can't provide me with that impossible thing? Then do not ask for an even bigger, more impossible thing.
As for favouring Exit over Voice, well, I already explained a bit of my objections to that idea earlier in the thread.
@Doctor Locketopus: Sure, if you are in a country that has those, and if you can get to one of them, and they are open when you have free time, and they haven't been closed down for budget or zoning reasons, and you don't get kicked out, you can get internet access. But that does not cover most people. As for acquiring older computers – sure, if you are surrounded by people who have computers, and you already magically know how to get an older computer working. Again, this does not cover most people. Unemployed people *sometimes* have a lot of time – but a lot gets taken up jumping through hoops to keep the lights on and keep yourself fed and in a home, not to mention looking for work. Also, this doesn't cover people who *are* employed, but don't make much money. The amount of education you need before the free education of the web or the library becomes really useful is, again, not something that everyone has. Even in the US, lots of places have failing schools, and lots of people don't have access to any relatives or friends that have the time and knowledge to show them the ropes. 'Access' is access to people or things that can help you out – for example, without access to an academic institute, I would have been paywalled out of basically every single journal article I have needed to seriosuly grow as a programmer. Without being able to speak like a hacker, I would not have had access to communities on IRC who have helped me to grow immensely as a programmer. Without access to some more knowledgeable friends, I would not have had the nice introduction to Vim that I had, and would probably still be using Nano like a barbarian.
In short, you are wrong about these things being both easy and universal.
" Sure, if you are in a country that has those, and if you can get to one of them"
Keep shifting the goalposts. It's quite amusing. Once again you are arguing that because the present system isn't perfect (an impossibly high bar, needless to say) that this somehow makes your system of enforced "equality" better. It doesn't work that way. Enforced "equality" winds up making everybody (except the people on top) impoverished slaves. Every time. For my part, 100 million dead bodies sacrificed on the altar of socialism is more than enough, but apparently that isn't the case for you.
" I would have been paywalled out of basically every single journal article I have needed to seriosuly grow as a programmer"
This is total crap. I'd be willing to bet that the majority of working programmers in the world have never read a single paper in a research journal in their lives.
@Doctor Locketopus: So, your response to 'here are some problems with hacker culture' is to say apropos of nothing, that I am somehow shifting the goalposts, then call me Stalin, then claim that programmers don't need to know things. Sure, whatever. *plonk*
" is to say apropos of nothing, that I am somehow shifting the goalposts, then call me Stalin, then claim that programmers don't need to know things. "
Translation: "I will now start lying about what you said, even though your original words are still there for all to read". To be specific, I never "claimed that programmers don't need to know things". That is a lie, and you are a liar.
Plonk, indeed.
Erik on 2015-11-15 at 11:23:58 said:
"…then claim that programmers don't need to know things. Sure, whatever."
No, the claim that programmers don't need to know things in paywalled journals.
The fact that you have difficulty telling these apart suggests that you have a view of programmer-as-expensive-certification; something you get with a sheepskin saying that you've completed the official programming course and written a formal programming thesis that cites recognized programming papers in paywalled programming journals and are therefore a true and real programmer.
If that's your view of programming, I can see why you'd want more scholarships to teach programming and grant official recognition to the disadvantaged.
But to most of the hacker community, such a view is complete and utter nonsense. It's like saying that you need to be a nutritionist to prepare a dinner for yourself. It's like saying that you can't drive a car unless you also participate in Formula 1. It's a view that's going to largely face incomprehension, not argument, because to a lot of programmers, suits, droids and their ilk in advanced formal education are not viewed as knowledge-bearers in the first place outside of a few select places like the maths and physics departments.
Anything behind a paywall should be assumed completely irrelevant to learning programming as it is viewed around here.
>Anything behind a paywall should be assumed completely irrelevant to learning programming as it is viewed around here.
I agree. I've never read a paywalled paper. Didn't finish college, for that matter. No formal CS or programming instruction whatsoever except I once audited a grad-level seminar on ontology-building because a friend of mine was teaching it (and found I already knew most of the material, which didn't surprise her).
OK, so it's a question open for debate whether I'm merely an exceptionally capable programmer or a freak outlier genius. (No, I'm not sure of the answer to that one myself.) If the latter, then my experience can't be used to generalize about people outside the extreme right end of the bell curve.
Still, the conclusion that we can reach is that either (a) I'm a freak outlier genius, or (b) credentialitis, paywalled papers, and indeed most of the formal apparatus we've developed to teach programming – is mostly bullshit unrelated to the actual learning process of good programmers.
I incline towards position (b). But I seldom say that very loudly because (a) might be true and I should shut up lest I give misleading advice to the less bright.
mdc on 2015-11-15 at 11:32:39 said:
This seems like the sort of problem that bazaars are born to route around. Successfully replacing meritocratic recruitment with political recruitment in one organisation may destroy that organisation but another will take its place, probably with all the same people who were removed from the first organisation. Even if these politics people are completely successful taking over all existing organisations, in a few years there will be a new ecosystem of organisations that have been specifically selected for their hostility to political infiltrators.
This sort of political action only works where monopoly is guaranteed by law, as in government employment, or at least there is a lot of inertia and incumbency advantage built in, as with large corporations.
I am not saying that the politics people can't make a mess and waste a lot of resources and time in the short term, not to mention destroy well-loved brands and the history associated with them. I am saying that they not only can't ultimately win but will produce a culture that is much more hostile to them than before they started.
@Erik: It isn't 'you can't make dinner without being a nutritionist', it is 'if you want to get to the point where you are a Michelin Star level chef, you will probably need some kind of formal knowledge of cooking'. Like, I didn't need stuff in journals when I was just starting out – I needed it to get as good as I am now, more than twenty years in to being a programmer. Anyone that promotes merit should want to see more people becoming good programmers, rather than fewer. Also, claiming that eg John McCarthy and others like him are simply suits or a droids, and not knowledge-bearers, is delusional. So much of the pearls of programming knowledge are locked up behind paywalls.
@mdc: You are fundamentaly wrong. Externalities exist, there is already a political fight over what 'merit' means, and the currently existing hacker groups are just as fiercly political about this as the groups trying to challenge them and change them.
@ Harold: The context is here https://twitter.com/elia/status/611319469982527488 It was about gender reassignment surgery, including for children, e.g. "I still fail to see how that kind of invasive surgery on kids can b cherished".
This provides insufficient context, as we're only seeing the last bit of the discussion. It kinda, maybe looks like Elia is maybe being a little prejudiced, but without the first part of the discussion it's really hard to form a reliable judgment.
Troutwaxer: I noted the same problem, but someone who knows more about Twitter than me will have to trace back the conversation. That said, I linked the specific part that Coraline was pointing to and shrieking about (http://www.amazon.com/product/dp/9527065682/), to which she didn't feel the need to add any context. So it should do for now.
"Like, I didn't need stuff in journals when I was just starting out – I needed it to get as good as I am now, more than twenty years in to being a programmer."
Here again, you're shifting the context. "Just starting out" is exactly the situation we're discussing, not "twenty years into being a programmer".
If you are already working as a programmer and actually do need something in a paywalled journal, then you'll have money to pay for it.
But, you know, there are an awful lot of people out there paying the bills by slapping together CRUD apps. Probability of those people needing something in a paywalled journal: zero, or nearly so.
@flaviusb: > we have some people (like Linus) who are happy to argue from authority
Linus doesn't argue from authority. He argues from technical merit. When he rakes someone over the coals, it's not because he's an "authority" and they're not; it's because they did something stupid that, if he hadn't caught it and stopped it, would have made the Linux kernel technically deficient.
> they (for example) don't understand security at all, and their authority lets them mandate this flawed understanding as the basis for kernel security going forwards, leading to all of our devices being permafucked.
Garrett on 2015-11-15 at 12:47:53 said:
Two thoughts:
1) How about taking the SCOTUS death-penalty model* to these systematic discussions?
2) I don't accept the premise**, but generally any member of the public can read pay-walled journals for free at a local college/university library.
* In the US, there have been a number of cases taken to the Supreme Court of the US claiming that the death penalty was unconstitutional because $METHOD of administering the death penalty fell into the category of "Cruel and unusual punishment", prohibited by the US constitution. The resolution the Court came up with was to say that the death penalty wasn't prohibited in and of itself. And, if somebody wanted to claim that the current method of implementing the death penalty was cruel, they would have to come to court with a proposed alternative instead.
** I read only a handful of paywalled journal publications in college, and that was because I took a deep and narrow dive into certain aspects of number theory. I've read more journal articles as an EMT trying to improve my knowledge.
Datum: My formal programming instruction was a year of incanting "public static void main string args" a hundred times in a hundred Java files, while endlessly cursing Java for not having various Lisp features I had come to take for granted. I had previously picked up the Lisp entirely informally, this in the days long before there was any such thing as Stack Exchange.
Which brings me to another point. The development of helpful utilities such as Stack Exchange and Google, the cheapness of internet and computing power, the ubiquity and display capacity of cellphones, etc. are all facilitating access far more effectively than I expect any political movement could do, also with less vitriol.
Programmers are fixing their end in making programming easily accessible to anyone who can read. Others, such as cellphone producers, are helping out in their way. Literacy is someone else's end. It is very unfortunate that there are still illiterates around, but that one's not on the programmers. Ask for contributions to fix that and you might get some. Try to make demands or impose obligations on a particular community to fix all the world's problems and you'll rightly be told to sod off for a myriad of reasons.
@Rick Moen:
FWIW, Matthew Garrett doesn't claim he's forking the kernel.
@flaviusb: There might be a political fight about what meritocracy means within individual organisations but in the bazaar model the winner is chosen by which organisations prosper in free competition, not by the outcome of the political battles within individual organisations. Even if almost all organisations agree about going down a blind alley it doesn't matter because they will lose to the handful that don't.
I notice that the "SJW" side in the political battle has not been able to create any successful organisation of its own. Its strategy is based wholly upon taking control of already successful organisations. I infer, perhaps wrongly but I think with high probability of being right, that the people the "SJW"s want to install are simply less capable and that their view of what is meritocracy is wrong. I believe with somewhat lower but still high confidence that they know that it is wrong, do not believe in meritocracy at all, and only claim they do as a smokescreen, and therefore that there is no real battle within organisations about the definition of meritocracy.
I think what the "SJW"s fundamentally don't get is that they are not dealing with a big bureaucracy here. What they are doing works when you are trying to redirect the government or a big corporation that has ten or twenty years of ruin in it. It does not work in the wheeler-dealer anarcho-capitalist outpost of open source. Politics takes a back seat to merit at the structural level not at the level of individual organisations. This is a fight they cannot win unless the people they are promoting are genuinely better than the ones they are attacking and if that were true they wouldn't need to, and would have no interest in, co-opting existing organisations rather than creating their own.
Patrick Maupin: "SJWs Always Lie".
Reading the article you linked to, it's clear it's a fork, even if he's not calling it that. Which is not the same as "forking it", but he's not stating what he expects to happen after he gets a set of things done. I would guess initially it would be to enhance the ability of distros to "deep-throat Microsoft" as Linus so elegantly put it.
Nb. people are trying to switch to *open access* (not paywalled) journals, mostly due to [censored] unconstrained greed of publishers (making e.g. electronic version of the journal more expensive).
On high end of programming you probably find yourself implementing ideas presented in journal articles (e.g. EWAH bitmap in JGit, then Git, see e.g. [1]), but I doubt that paywalled journals are the only source of idea.
[1]: http://githubengineering.com/counting-objects/
> It was about gender reassignment surgery, including for children, e.g. "I still fail to see how that kind of invasive surgery on kids can b cherished".
The problem is that any argument relying on the assumption that this actually happens is, as far as I know, at best ignorant and at worst a straw man.
Which incidentally makes his remark actually significantly worse than I had assumed it was.
@ Random832:
I think we need to see the whole discussion before we make any judgments. I'm not going to decide about anything if I know there's evidence I haven't seen.
That being said, I am also dubious about gender reassignment surgery on children, not for any anti-trans reasons, but because one can expect brain chemistry changes, including hormonal changes, plus large amounts of brain development during puberty. Until we know the exact cause (causes? there may be more than one) of transgenderism, I'd be very leery of gender reassignment surgery on children.
These doubts are why I really want to see the conversation that leads up to the comment; I might agree with Elia.
In this respect you resemble my father, who really is an outlier genius and who made a successful (still ongoing) career in mechanical engineering despite having only about a semester's worth of university credit to his name.
My suspicion is that code sings to you; you do not need academic papers because you can look at the code and glean the concepts directly from the code itself. With sufficient practice one can look at a page full of cryptic symbols, identify familiar patterns, and thereby discover new concepts when the programmer arranges these patterns in an unusual way; but it takes practice, and practice requires dedication, and dedication requires a certain fascination which not many people will have.
And it's this way in every discipline. The average person starts a game of Pac-Man, dies a few times, and gives up because the frustration of failure overwhelms the fun in playing. But world-champion Pac-Man players have kept playing until they reach a level where they can not only identify abstract patterns in the enemy AI (and, like programmers, give them clever names like "cruise elroy" for the speedup the red ghost undergoes after some time in any level), but manipulate the ghosts to set them up to be eaten, or to avoid Pac-Man completely so the player can take a piss break.
It's possible for a sufficiently clever layman to teach themselves programming. But in my experience, without the benefit of a formal program they usually don't make it much past the "Visual Basic" stage of development. They know how to string statements together to get basic tasks done, but when it comes to composing abstract concepts and turning them into code which instantiates them in the machine, they are still at a very low level. The concepts have to be presented to them, as the GoF did in Design Patterns, before they can work with them. Fortunately, the market is still huge for programmers at this level of capability and it's possible to make a very comfortable living this way.
Remember when some of us were bickering in blog threads about UIs and I kept insisting that I thought Linux was just fine the way it is, UI-wise, but I'm weird and different and what I say should not be construed as to apply to ordinary rank-and-file users, who for the most part could never suffer through the clusterfuck that passes for "UI design" in the open source world? Welcome to why. In the time it takes me to figure out which mouse gestures do what in Windows or GNOME, I've already composed a command or pipeline in my head and it's just a matter of typing it in, so consequently I loathe "desktop environments" with the fire of a thousand suns, and am much more at home at the command line or even a primitive X environment from 1995. But my sister cannot operate in that realm at all (she's even one of those who get frustrated the first time they die in a video game), so she will always stick with Windows or Macintosh machines.
>My suspicion is that code sings to you; you do not need academic papers because you can look at the code and glean the concepts directly from the code itself.
Um, duh. I assume that anyone above junior-programmer level has this experience at least some of the time. I would find it a bit disturbing and upsetting if anyone convinced me that only freak outlier geniuses do.
…though I probably wouldn't agree with how he phrased things – the "not seeing reality" comment is probably undiplomatic.
Scientists have taken to using the hashtag #ICanHasPDF as a surreptitious message to their colleagues: "Please pirate this paper by downloading it from your university and sending me an electronic copy." They seem unfazed by the fact that this is what Aaron Swartz faced felony charges for doing (albeit at a much greater scale).
And the journals really are that bad. Elsevier are the scum of the earth; in addition to the money squeeze, they were the ones who set up a vanity publication for Merck to push Vioxx through the FDA and onto the market without adequate research being done into its safety and efficacy.
@Harold:
Anybody who has code that Linus isn't currently willing to incorporate in the kernel has to maintain their own tree. But sometimes things change later and the code (or a modified version thereof) becomes acceptable (perhaps because of the mods; perhaps partly because the same need is later recognized by others). Look at some of the early changes google made with Android.
There's a difference between a temporary fork and forking the project. The first one is expediency; the second one is an attempt at a coup. Despite Garrett proudly claiming to be an SJW (does he really understand all that entails), the article doesn't read like he's looking to create a coup. I dunno — haven't really kept up with it otherwise. But, it's a heck of a lot of work to maintain a parallel tree, and even with the resources google could throw at Android they were begging to get their code back in the main tree. I haven't seen anything to suggest that Garrett doesn't want his code there, either.
If you had asked for a rigorous definition of merit, I would counter by asking you for something that is surely simpler, as it is a restricted form of that question: [solve the halting problem]?
Once again you state something that makes be suspect that, despite your statements to the contrary, you are indeed seeking perfection from others. Every time I look, you seem to have said in slightly different terms, "I'm not a perfectionist but [nothing less than perfection is demanded]." I wish you the best of luck with that, but I've no interest in hearing anything else you have to say now.
…either (a) I'm a freak outlier genius, or (b) credentialitis, paywalled papers, and indeed most of the formal apparatus we've developed to teach programming — is mostly bullshit unrelated to the actual learning process…
Here's an interesting statistic: just over one quarter of college graduates work in a job whose duties are related to their major—the example given is whether a Communications major works as a public relations manager or retail salesperson. Given this information, I can only conclude that either the value proposition of a college degree is mostly uniform across various fields of study (for example, as proof of a particular work/study ethic) or not directly related to the credential itself (networking with people, rite of passage).
However, in either case, this strongly implies that the "credentialitis" and formal educational apparatus are currently given mis-attributed esteem or praise. (This is given further credence when you consider the number of very famous college dropouts who went on to lead a major technology firms. Gates, Jobs, Zuckerberg? Heck, the statistics almost make it seem as if you should drop out of college if you want to be rich and famous in tech!)
My unfortunate suspicion is that only "freak outlier geniuses" experience this without benefit of formalized education; and I know for a fact that there are plenty of people well above junior programmer level who experience it rarely or not at all. Look for managers, "software architects", or senior programmers who are fond of giving stern lectures to young programmers about how code has no value in itself and how it's the business that truly matters.
> only "freak outlier geniuses" experience this without benefit of formalized education
It's certainly possible that the right education (formal or informal) can help with this, but IMO the primary prerequisite to seeing the code sing is the willingness to put in enough hours looking at code. And by "looking at" I mean editing, moving around, thinking about how you would do it — is there a better way?, thinking about what constraints, real or imagined, caused the code to look as it does now, etc…
IMO, to become really good, you don't have to be a genius, but you do have to have a passion that extends past work hours.
>With sufficient practice one can look at a page full of cryptic symbols, identify familiar patterns, and thereby discover new concepts
You should try playing Dwarf Fortress sometime. It is that comment turned up to somewhere between 11 and Graham's number.
*reads about Linux fork*
"getting Linux boot and install on PCs locked down with Windows 8's UEFI"
*Locks self in cupboard and screams expletives for half-hour*
What if I told you… that this and what we call "genius" are the same thing?
>What if I told you… that [a passion that extends past work hours] and what we call "genius" are the same thing?
I don't believe it. Passion, translating into time invested, is not enough to make genius.
An extreme case to illustrate the problem: suppose you managed to teach Logo, or some other ultra-simple instructional language, to someone with a dramatically subnormal IQ, say 85 or so, and by doing so infect that person with a passion for programming. Now add 15 years. Think you'll get a genius programmer? Not going to happen – your victim simply can't handle long enough inference chains, and can't learn new tools fast enough or well enough. You'd have perpetrated a kind of cruelty.
The theory that genius is just perspiration is very beguiling; it appeals to our egalitarian cultural values. I don't believe it; I've known too many geniuses myself, and there's a difference that "passion" doesn't capture, a quality you can't get by sweating. I'm not sure IQ is an entire measure of it, but it's certainly implicated.
@Jeff Read: > this and what we call "genius" are the same thing?
I would partially agree and partially disagree — the hours are necessary in most cases, but certainly not sufficient in all cases. I know a lot of people who could put in the hours and still come up empty-handed. To your point of education, though, as with anything else, having (the correct) others around to guide you when you are putting in your first several hundred hours could certainly be a good thing.
On the flip side, I know a lot of people (men and women) who are more than smart enough to become computer geniuses, but who are not at all interested in that, and are smart enough to apply their energies where their passions lie.
Well, I have certainly (and unfortunately) encountered negative side of examining source code of inexperienced programmers. My eyes, they burn… ;-)
@Jeff Read: My unfortunate suspicion is that only "freak outlier geniuses" experience this without benefit of formalized education
FWIW, I don't consider myself a "freak outlier genius"–just smart :-)–and I am entirely self-taught as a programmer, but I have had the experience being described plenty of times. I think, as Patrick Maupin said in response to you, the key is not "genius" but enjoying programming enough to put in the time.
Look for managers, "software architects", or senior programmers who are fond of giving stern lectures to young programmers about how code has no value in itself and how it's the business that truly matters.
IMO this is just people rising to their level of incompetence. I don't need to be lectured about how code has no value in itself; in fact I just spent a week or so throwing away a bunch of code I'd written for a project because it was clear it wasn't doing the job. But it's still the programmer who needs to do that, and the key to doing it is not "genius" but having enough pride in your work to know when it needs to be redone.
@esr: Passion, translating into time invested, is not enough to make genius.
To clarify the post I just made before reading this :-), I don't think passion (or love of programming), translated into time invested, is enough to make genius. I think the experience that was described earlier, of having code "sing to you", does not require genius. It may need less time invested in order to have it if you're a genius, but it's not inaccessible if you're not.
>It may need less time invested in order to have it if you're a genius, but it's not inaccessible if you're not.
Agreed. I don't expect that all intermediate- and senior-level programmers (which I expect should hear the song at least part of the time) are geniuses.
@Jakub Narebski: My eyes, they burn… ;-)
Yeah. Sometimes a break from Stack Overflow is in order.
@Alex K:
> Gates, Jobs, Zuckerberg?
Yeah, to conflate these two threads, if you drop out of college to follow your passion and are passionate enough to put in the hours, there is a chance that good things will happen. Several women have done the same thing, but for the most part they are not in STEM.
According to one list, the thirty most successful dropouts were often technical and, with the exception of the embattled Elizabeth Holmes, all male.
But to most of the hacker community, such a view is complete and utter nonsense.
A potentially practical idea: I think it's blatantly obvious to experienced hackers that formal education is not a prerequisite to successfully inventing and building new things, that informal tinkering of some variety is, and that there undoubtedly do exist some individuals who have the potential to make worthwhile contributions but for whatever reasons (and for youth especially, I'm willing to entertain the concept of "lack of ready access" to the core material requirements, such as computers with Internet connections in environments appropriate to hacking, which libraries often can't provide).
Given that, it seems that one possibly effective approach would be to support the development of maker spaces accessible to interested but disadvantaged youth or even adults—basic computers with standard programming tools, a decent Internet connection, a simple electronics workbench, and the like. The ones I'm familiar with seem to be today's analog of the university electronics and computer clubs that nurtured Eric's generation of hackers, and the actual capital investment to set one up would be fairly low (the biggest cost being rent/office-type expenses and labor for supervision, which might very well be volunteer).
>Given that, it seems that one possibly effective approach would be to support the development of maker spaces accessible to interested but disadvantaged youth or even adults—basic computers with standard programming tools, a decent Internet connection, a simple electronics workbench, and the like.
Note that we generally didn't have computer clubs per se. What we had was 24/7 access to terminal rooms, and lots of opportunities to work near other people who were learning in the same way we were.
What we had was 24/7 access to terminal rooms, and lots of opportunities to work near other people who were learning in the same way we were.
That sort of environment is what I think the ideal maker space could be in today's technological milieu. The two main bits that I see as important that library access really doesn't provide are the unconventional hours (maybe 24/7 isn't always practical, but the most likely hours for youth to be tinkering are nights and weekends, not 9-5 M-F) and the physical environment for interaction. These days a significant chunk of that "working near people" is more virtual than physical, but access to a variety of communication channels, especially IRC and video chats in addition to Web-based resources like Stack Overflow, doesn't fit with the traditional and still predominant "shh, it's a library" model.
>These days a significant chunk of that "working near people" is more virtual than physical,
While this is true, I think being able to hang with peers on a similar learning track in meatspace has advantages not to be underestimated.
Yeah, I toyed with trying to set up a hackerspace-like-substance around here. I don't think it can be done standalone — rents are too high. Finding the right partner is paramount. As you point out, libraries are an obvious but problematic possibility. Schools (both public and community college) and churches also have pros and cons. All it should take is the right pitch to the right person at any of these to relate it to their mission.
Ellie Kesselman on 2015-11-15 at 23:51:36 said:
Alex K: Good for you, for reading Liberty Street Economics blog! It is one of my very favorites. I am using this opportunity to tell you how much I like your bluebird avatar :o)
Troutwaxer's tone reminds me of a more leftward-leaning version of a sea lion.
John on 2015-11-16 at 00:15:50 said:
"In this climate of economic uncertainty, America is once again turning to innovation as the way to ensure a prosperous future."
"Yet innovation remains tightly coupled with Science, Technology, Engineering and Math – the STEM subjects. Art + Design are poised to transform our economy in the 21st century just as science and technology did in the last century."
"We need to add Art + Design to the equation — to transform STEM into STEAM."
http://stemtosteam.org
I didn't intend to. But the skill space is so wide now (languages, toolsets, even target platforms like Unix/Web/Arduino/Pi/Beagle) that good Internet comms are necessary-but-not-sufficient in a way that they weren't when "Unix and core TCP/IP" covered most of the territory.
Erbo on 2015-11-16 at 01:13:12 said:
This is the "code of conduct" that I will be adopting in all of my projects henceforth:
The one and only criterion that will be used to determine whether a contribution to this project will be accepted is the quality of the contribution and how well it solves the problem it was contributed to solve. Period.
I do not give one milli-micro-nano-fraction of a fuck what race you are, what gender you are or identify as, who you want to sleep with, how old you are, what your height or weight is, what if anything may be different about your body or brain, what language you speak, what country you're from, what God you pray to, where you work, how much money you have, et fucking cetera. Is your contribution any good? That's all that matters.
There is one exception to the above rule: If you're an asshole, you're banned from the project. Permanently.
If your contribution is not accepted, and you start whining about how it's "actually" because you're of some-or-other gender/race/religion/nationality/whatthefuckever, you are attempting to have the deck stacked in your favor because you're "special." That makes you an
asshole. And you're gone.
This project explicitly rejects the "Open Code of Conduct" as published by the TODO Group, and any similar "codes of conduct" that may be promulgated. Anyone complaining about this is an asshole, because who the fuck are you to tell me how I should run my goddamn project? And you're gone.
I reserve the right to change this as I see fit…but anyone who tries to force me to change it in ways that are offensive to me is an asshole. And they're gone.
@Erbo. Okay, now: someone reports to you that someone else, in a forum where they have attached the project's name to their words, is being an asshole. What do?
Or did you mean to suggest that believing that one's contribution has been rejected due to their race/etc is the only relevant way in which it is possible to be an asshole?
> That being said, I am also dubious about gender reassignment surgery on children, not for any anti-trans reasons, but because one can expect brain chemistry changes, including hormonal changes, plus large amounts of brain development during puberty. Until we know the exact cause (causes? there may be more than one) of transgenderism, I'd be very leery of gender reassignment surgery on children.
I think you weren't paying attention. The problem wasn't that he doesn't think it should happen, the problem is that he thinks it does happen and/or thinks his opponents do think it should happen.
esr: Bear in mind that if you consider 85 IQ to be "dramatically subnormal" then the vast majority of mid and senior level professional programmers are correspondingly geniuses. About 16% of the population has an IQ lower than 85; are 16% of the population clever enough to be mid or senior level professional programmers?
And the original comments and outrage were indeed based on utter (and willful?) ignorance. What happens is that puberty is delayed for children who have been able to convince a lot of others they suffer. The irreversible changes are started at a later age.
New Dutch study supports delaying puberty for transgender youth
http://www.dailykos.com/story/2014/9/11/1329035/-New-Dutch-study-supports-delaying-puberty-for-transgender-youth
It seems Leo wasn't held back by these problems: http://www.businessinsider.com/leo-the-homeless-coder-2015-2015-4?IR=T
(Although it is weird he doesn't want to claim the money he earned, get a place, and so on.)
Look, overcoming obstacles IS a good filter. What is your ideal idea of a talent – just natural born high IQ people who have education, mentoring, everything dropped at them? It is horribly cliche but obstacles, difficulties are character building. Come to think of it, I saw a certain pattern of upper class people who had it too easy and all the education and "chances" dropped at them and lacked difficulties, tended to quit (I am talking about employment corporate programming, not hacking) when a project became hard in an endless yak-shaving racing with a deadline way.
Learning programming while unemployment, homeless, black, whatever IS a good signal.
So what is exactly wrong in having obstacles to overcome? I have heard that in the USA Ivy League universities aren't just looking for a perfect high school record but also things like sports performance or charitable work – something that is at some level difficult for coddled upper class people and signals more character strength, more ability to deal with difficulties?
So, the flip side of the coin is do you really want to make things easy for everybody in which case how do you test for things like ability to persevere?
@ESR before we start stroking your genius, it is important to point out that a genius could independently reinvent various programming paradigms but the implementation will differ enough to annoy the living bejeezus out of people trying to read that code. Programmers are famously easy to annoy this way, some even get all worked up about spaces vs. tabs in indentation. Since nobody complains your code is hard to read, we can assume you haven't magically reinvented accepted standards and code style but simply that you learned most things by immersion back then, similar to how people learn human languages in an efficient way.
I always figured pattern matching is usually better than explicit logical reasoning (the mind still runs logic but as a background process, becoming conscious only when fitting looking patterns don't fit), that is why I believe in learning by imitation, as in, don't explain much just show me examples way.
"asshole" in practice means the the first person to stop cheering Bruce Jenner is deemed an asshole, thus loses his job and can never get another one, leading to the Stalin problem that no one dares to stop cheering Bruce Jenner.
We know that triggering puberty before its normal time has large and serious side effects. Girls permanently lose a lot of potential IQ. No one really knows what the effect of delaying puberty to beyond its normal time is. Maybe it is harmless or beneficial. Maybe we should delay everyone's puberty. But today, even if ninety percent of those who suffered delayed puberty wound up has horrible freaks who usually committed suciide, no one would dare mention the fact, just as no one dares mention the fact that most male homosexual "families" are harems of sex slaves, that the prognosis for children raised by homosexuals is extremely bad, and most male to female transexuals suffer an early death due to violence, drug abuses, or, most commonly, suicide.
@JAD (James Donald)
" But today, even if ninety percent of those who suffered delayed puberty wound up has horrible freaks who usually committed suciide, no one would dare mention the fact, just as no one dares mention the fact that most male homosexual "families" are harems of sex slaves, that the prognosis for children raised by homosexuals is extremely bad, and most male to female transexuals suffer an early death due to violence, drug abuses, or, most commonly, suicide."
It is clear that your fantasies are haunting you. I think you should seek professional help. Really, it can benefit you too.
For other interested readers, just read the report:
http://pediatrics.aappublications.org/content/early/2014/09/02/peds.2013-2958.abstract
@JAD on early puberty: seems to be an effect of fscked up childhoods, abusive parents, ghetto etc. that kind of stress speeds it up and is generally a part of Fast Life History Strategy which is basically the 2010, evolution-backed, really worked out version of the old sociological research on time preference in the 1960's that everybody who wasn't blinded by PC loved (Banfield – The Unheavenly City Revisited and these stuff back then, now out of print). I can really wholeheartedly recommend these 6 articles, one could build a whole ideology just on these: https://www.psychologytoday.com/blog/beautiful-minds/201007/life-in-the-fast-lane-part-i-evolution-the-fast-life
Giulio Prisco on 2015-11-16 at 06:27:27 said:
Bravo Eric, well said. The open source community has, so far, resisted SJW attacks and affirmed the obvious: everyone is welcome to contribute, regardless of their skin color, gender, and sexual orientation (all of which are irrelevant), and all contributions are selected uniquely on the basis of their quality. Let's keep it so.
@Erbo is right – just the same way as explict GPL or Mozilla or similar licencing was/is a better idea than just throwing everything into public domain, the correct way to fight these awful Codes of Conduct is to make one of yours – for example it could contain just these rules, contributions should be relevant and high quality, and communication should be constructive, on-topic and non-flamey (I think hackers have these types of unwritten rules since Usenet times?) write it down, call it the Cod of Conduct with a cod fish logo because you guys seem to love such silly puns and I think it gets a bit of intended mockery through right, and advertise it loudly as a signal of being an SJW-free project.
Even put the cod fish logo on the project front page just to send out the signal. This is the type of stuff you hackers seem to like.
Understand that it is far harder for them to push theirs if there is already one in place.
@ESR you seem to be just the right guy to push something like this.
>@ESR you seem to be just the right guy to push something like this.
Agreed. Meredith, Roberto, Rick Moen, Ken Burnside, and myself are working on it.
How'd this go?
A friend has just had a free software project take off, and I'd _love_ to recommend a sane code of conduct to him.
> call it the Cod of Conduct with a cod fish logo
Consider this post a pre-order for several t-shirts should you adopt this strategy :)
Relatedly, I hope that everyone silently (or not so silently) encouraging ESR to publish a hacker-friendly cod of conduct (or whatever it will be called) has noticed the shiny Donate button on the top right hand side of the page ….
The Ivy League are looking to select future corporate and government bureaucrats, and corresponding entrepreneurs and politicians, who can kick back money and power to them in the future. They are not (primarily) looking for the best academics or voluntary work hacker-like people, who only have prestige to donate. So they set up these "Junior CEO" requirements that don't exist in other countries. Generally the people who meet them are upper middle class, as they are the ones who are accustomed to taking initiative and being leaders, and maybe have actual CEOs as family and friends to advise them.
pf on 2015-11-16 at 07:58:52 said:
There's a cult of meritocracy?
Does it enjoy constitutional protection in the U.S.? Is there a particular cult image for a shrine? Are there rituals for blessing a level playing field or invocations calling for dispassionate objectivity and a lack of favoritism from the gods? Does membership mean meritocratic donations are tax deductible?
And if you're a member of the cult, can you invoke the terms of a Contributor Covenant against the author of the introductory page on contributor-covenant.org for the alienating derogatory reference to your religion, or hasn't that site adopted a code of conduct?
The calm, assured tone and baiting presuppositions in the djangoconcardiff thread were very familiar. I don't associate it with a particular ideology, but rather with a particular kind of ideologue. Conversation with them is never productive, and I've never really worked out whether they're deliberate trolls or just kind of self absorbed.
Perhaps a member of the cult of meritocracy could use their holy symbol to "turn meretricious" and send such people away.
And while the Code of Merit linked above seemed a bit too wordy, a nice, concise Cod of Conduct could preemptively inoculate vulnerable projects against an obvious malady, and (with a suitable cod logo) would also make a decent decoration for a coffee mug.
Nelson Paul on 2015-11-16 at 08:02:43 said:
If a Chinese person wants to hang with another Chinese person for any reason that is a human preference and I don't think I'm entitled to dispute it. Not even if I'm excluded. Not even if they offer a service to Chinese people only. Straight and gay also. Men and women too. There is no violence. No theft. Individuals are not only fully entitled to discriminate they are biologically required to do so on whatever basis they choose. If they weren't we wouldn't be alive today.
Free software is not about social justice it's about using transparency to reject involuntary subversion and enslavement.
ams on 2015-11-16 at 08:19:00 said:
One thing about programming that made it very easy, and even compelling to learn (and I'm not (primarily) a programmer) was the immediacy of feedback. If you want to code something for a computer to do, you hack it together, run it, then look at the results. Then iterate, until it does what you want it to do. Not just syntax errors (which your compiler will make you aware of), but what all the pieces are really doing, and how you need to change them to make them do what you intended.
Compare with learning a dry discipline like certain kinds of math, or statistical mechanics, or things like that: Sure, there are pictures/processes you can use to see what is going on in your head, but the entire working of the problem has to live in your head. There's no helpful flawlessly logical thing showing you what happens if … all the time.
… Well, until recently, which leads back to programming, and the other reason why it interests me. It lets me see how the models work, which leads to much faster understanding.
Compare learning orbital mechanics the way Kepler and Euler had to do it, with learning orbital mechanics via Kerbal Space Program. KSP provides you with rich and immediate feedback about the domain of the problem, sending it straight into your cerebellum as intuitive understanding. If you have that, you can learn the math easily without being turned around.
Without an intuitive picture, you have to be very careful with your formal system, because if anything breaks you're lost and have no picture of what is going on.
At least, that's how I learn.
I have always used to think that codes of conduct are for children. For dealing with actual and functional children they can be helpful, but these are not the sort of people you want to have to babysit in open source in the first place.
Also: All the things we learned in aerospace engineering undergrad years ago (90% of which was crammed in one ear and fell out the other in 23 credit hour cram semesters) to learning how to fly a real plane recently.
Everything has become concrete, sitting in the cockpit of an actual aircraft, using actual instruments, interacting with actual air traffic control, preflight checking the real control systems. It is worlds different in terms of the level of understanding I can maintain when I have actual experience with the domain.
It makes me wonder about some of my peers who never see the outside of an entirely abstract systems engineering labs. The story of how the founders of Bell Helicopter designed their first vehicle: They built it, crashed it, rebuilt it, crashed it, performed tethered flights, untethered flights, attached flywheel stabilizer things, adjusted weights. Then they hacked together the drawings.
'but Nelson, rejecting involuntary subversion and enslavement *is* social justice'
Need your definition of social justice then, because that's where we're going to disagree.
During that discussion you'll need to establish the right to not be discriminated against, in order to establish that discrimination is a matter for 'justice' at all. I've already argued, it isn't.
Social media and mass communication are rapidly changing the paradigm of cultural evolution that has been operating within our species for the past few millennia. Hacking is the root skill set for controlling these new levers of power in memetics. As such, the SJW invasion into hacking culture is no accident.
David Isecke on 2015-11-16 at 09:44:58 said:
To me, this all comes down to freedom of association. And that freedom means two things, the freedom to associate, without coercion, and the freedom to NOT associate, without coercion.
The latter of the two ideas is arguably the more important.
So I'd probably just say something along the lines of, "I value contributions based on their technical merits, in accordance with my vision for , and I appreciate not even having to think about your identity as a . But, while I fully intend to do my best to be as welcoming and helpful as my time permits, and to ban rarely, I reserve the ultimate right to not accept contributions, or ban someone from my blogs, wikis, or talk groups, for any reason at all. If you disagree, you are free to fork the project."
Hmm.. it seems that ( insert project name ) and ( insert identity group name ) got automatically stripped out, so please add those to the previous comment at the proper places. :)
@David Isecke
> If you disagree, you are free to fork the project."
Are you telling dissenters to fork off?
@Jessica Boxer
I believe I am!
@Random832 – "Okay, now: someone reports to you that someone else, in a forum where they have attached the project's name to their words, is being an asshole. What do?"
Stipulated: I can only make rules for a project I control. Anyone else's project or forum has their own rules, and it's not up to me to enforce them; I'm not the Internet Police. Therefore, the most I would do is disavow them speaking for the project, unless I have empowered them to do so (unlikely). If they're being an asshole someplace else, let whoever runs that other place lower the boom on them.
Worse: If I go banning people as "assholes" based on what amounts to hearsay, I leave myself open to a disinformation attack…which is exactly the kind of tactic that an SJW might use! At most, such a statement might warrant "keeping an eye" on somebody's behavior, to more quickly spot if they're actually an "asshole" in my project.
(Of course, if Sally SJW behaves like an asshole to someone else's project, it's a good bet that she'll do the same to mine eventually. But this is not Minority Report and I can't and shouldn't engage in preemptive banning.)
Contrariwise: If someone brands themselves an asshole under my rules, the most I can do is ban them from my projects. I may choose to publicly "name and shame" them, but I would not recommend that anyone else preemptively ban those assholes as a result of my doing so. (Of course, they might do so anyway. I'm not the boss of them. But it's unwise of them to put that level of blind trust in me or anyone else.)
I may amend that code of conduct to clarify that point.
I find it sad and telling that so many SJW battles are about things so rare, theoretical, and ultimately trivial (though all are grouped under the banner of "civil rights" for political purposes). A reporter asks a pizza parlor if they'd cater a gay wedding and all hell breaks loose. I must have missed the civil rights crisis of gay couples who can't get pizza at their weddings. In fact, I must have missed all the gay weddings that included pizza.
The example above is even worse: someone voices polite and not unreasonable doubts about gender reassignment for children, and is pilloried. Such children are quite rare, and of course the topic has absolutely nothing to do with coding. It's depressingly similar to the Eich event. AFAIK nobody could point to a single incident of Eich ever being rude or discriminatory toward anyone, but that was not enough to save his career, because a few people "felt uncomfortable" about his Mormon belief in traditional marriage.
"The personal is political" is ultimately totalitarian.
" Paragraph 2 denounces the "pervasive cult of meritocracy".
THE SJW's wet dream:
( Somewhen in the future)
Attention: Will Mr. Harrison Bergeron and Mr. Eric Raymond, please report to the office of Handicapper General Glompers. Your handicapping requires adjustment.
Don on 2015-11-16 at 11:51:03 said:
The first lines of the quoted message should probably read:
"Nice project you got there. It would be a shame if something where to happen to it."
> Stipulated: I can only make rules for a project I control. Anyone else's project or forum has their own rules, and it's not up to me to enforce them; I'm not the Internet Police. Therefore, the most I would do is disavow them speaking for the project, unless I have empowered them to do so (unlikely).
And if they continue claiming to speak for the project?
I was actually more interested in the case where you [i]disagree[/i] that they're being an asshole, though. It sounded like you were inclined to punish the person reporting them to you out of spite, despite the complete lack of clarity as to what behavior you consider to make someone an "asshole" (because if you did have a list, that'd be a code of conduct).
> Worse: If I go banning people as "assholes" based on what amounts to hearsay
If it's a public place that you can go see yourself it's not hearsay
> Contrariwise: If someone brands themselves an asshole under my rules, the most I can do is ban them from my projects. I may choose to publicly "name and shame" them, but I would not recommend that anyone else preemptively ban those assholes as a result of my doing so. (Of course, they might do so anyway. I'm not the boss of them. But it's unwise of them to put that level of blind trust in me or anyone else.)
I'm a bit confused. I thought we were talking about public conduct – doing so would not imply trusting you, merely trusting the service providers involved not to falsify their public posts (which would be a serious crime)
I find it sad and telling that so many SJW battles are about things so rare, theoretical, and ultimately trivial (though all are grouped under the banner of "civil rights" for political purposes).
According to this article I read in my news feed this morning, this is because of a shift and (literall clash) of culture:
"It was once considered unbecoming, or annoying itself, to moan publicly about trifling personal ordeals. Now, in a seismic shift for the moral culture, abetted by technology, we tolerate and even encourage the 'microcomplaint': the petty, petulant kvetch about the quotidian."
"… conclusions drawn in a 2014 paper in the journal Comparative Sociology called 'Microaggression and Moral Cultures.' The authors Bradley Campbell and Jason Manning argue that the increased attention recently given to microaggressions is a result of 'the emergence of a victimhood culture that is distinct from the cultures of the past.'"
@Alex K.: It's an interesting question why that has become the case. I think there are many factors, but I suspect these are among them: 1) The rise of single-child families: only children are often a bit spoiled. 2) The rise of singe motherhood: children of single mothers are often indulged to a greater degree.
After my public disavowal of their words? In that case, they are deliberately trying to write checks that they know they can't cash and that I won't honor. That would make them an asshole. And they're gone.
But it's still someone else's project/forum. I don't enforce rules there. "Not my circus, not my monkeys." At least I know the reporter is accurate and not running a disinformation campaign, though.
"I thought we were talking about public conduct – doing so would not imply trusting you, merely trusting the service providers involved not to falsify their public posts (which would be a serious crime)"
I've called them an asshole as far as my own projects are concerned. They may or may not be an asshole elsewhere. (I'd bet they would, but I could be wrong.) Whether or not other projects want to take my word for it that a given person is an asshole is their business, not mine. I control only my own projects.
Nota bene, IIRC Linux kernel has Code of Conflict, not Code of Conduct…
@pf 'the calm, assured tone and baiting presuppositions in the djangocardiff thread were very familiar … a certain type of ideologue …. I've never worked out if they were trolls or just very self-absorbed.'
It's how mildly retarded career petty criminals think administrative memos should be written. Yes, some trolls and self-absorbed people write like this, but if you read stuff written by guys fresh from the joint and headed back, they all write like this. And it works- if that memo had gone to a Computing for Dummies 101 project it would probably have gotten some money or clout for the writer. Remember there are thousands of Computing for Dummies projects for every high-IQ computing project. They outnumber you, they have more power, and they know it.
flaviusb> Erasure: Christine Peterson coined the term 'open source', but people tend to remember it as being coined by ESR. This kind of thing happens with science, with code, with politics, and it means that we should at least take seriously the idea that merit is not recognised as such.
If that be so, then your problem with meritocracy is that we should be having more of it but don't. I don't see how this amounts to a rebuttal of Eric's points. He thinks we should have more meritocracy, too. The same applies, correspondingly, to the other examples in your post.
As an aside: a quick Google search shows that the Open-Source Initiative Eric founded does give proper credit to Christine Peterson for coining the term. So if the general public remembers it as being coined by Eric, how is that any fault of his or his fellow meritocrats at the Open-Source Initiative?
@ PapayaSF – "It's an interesting question why that has become the case."
Modeling suggests that it is primarily due to affluence and lack of existential threat or significant hardship in our daily lives. Evolution has built us to overcome difficulties in life, and without any significant hardship in our current environment, we often seek to overcome trivial (and often self-created) pseudo hardships. And you need lots of these to repair your self esteem; especially if you're sustaining yourself largely as parasite.
@TomA: I think that is part of it, too. Another aspect is something I believe I said earlier: reform movements all start with legitimate grievances, but as they achieve their goals, they tend to focus on smaller and smaller issues. Nobody sane thinks discrimination against blacks or gays is worse than it was 30 years ago, and yet the "civil rights" rhetoric has gotten more extreme. You'd think that the KKK was on the march. But self-appointed leaders want to lead, and people want to socially signal that they are against Bad Thinking, and so we have a lot of hysteria over Halloween costumes, microaggressions, and people's opinions of transgenderism.
And note that we are simultaneously told that 1) this is all just being polite, so what's the big deal?, and 2) it's all a crucial, life-and-death civil rights struggle equivalent to slavery and lynching. Some Black Lives Matter types have now started the #FuckParis hashtag because the media focus shifted away from trivial events at the University of Missouri.
(P.S.: It's interesting to note that the media attention on the Missouri football team a year or two ago had to do with sexual assaults and rapes by players. Now all that is forgotten, and they are now victims of racism because of what one drunk guy said, the notorious "cotton ball" incident, and a poop swastika of unknown provenance which is somehow assumed to be anti-black.)
> As an aside: a quick Google search shows that the Open-Source Initiative Eric founded does give proper credit to Christine Peterson for coining the term. So if the general public remembers it as being coined by Eric, how is that any fault of his or his fellow meritocrats at the Open-Source Initiative?
Why does it not being his fault equate to it not being a problem?
So far no one has demonstrated that "the general public" or anyone else remembers the term "open source" as having been coined by Eric. Citing a problem which isn't actually a problem proves nothing.
>So far no one has demonstrated that "the general public" or anyone else remembers the term "open source" as having been coined by Eric.
Unfortunately, I have encountered this misconception; I am always at pains to correct it, and Christine knows this.
But that is basically irrelevant. That we have trouble achieving anything like perfect meritocracy is no reason to stop trying to approximate it as closely as possible.
> But that is basically irrelevant. That we have trouble achieving anything like perfect meritocracy is no reason to stop trying to approximate it as closely as possible.
See, this is where you're getting tied up in rhetorical knots with what you believe they believe and with what they believe and with what you believe what they say means.
The problem is, they think their proposed policies will do a better job of approximating a real meritocracy, by removing "this is a meritocracy" as a thought-terminating-cliche that allows the established contributors of each project to avoid having to justify rejecting any contribution they feel like rejecting whereas the real reasons for the rejections, the SJWs suspect, are influenced by the established contributors' biases towards different groups of people.
>whereas the real reasons for the rejections, the SJWs suspect, are influenced by the established contributors' biases towards different groups of people.
But, in reality, the SJWs are completely full of shit about this. There is a reality here; it's not just conflicting narratives all the way down.
esr> Unfortunately, I have encountered this misconception; I am always at pains to correct it, and Christine knows this.
I agree this is irrelevant to your core point: imperfectly-accomplished meritocracy calls for more meritocracy, not for abandoning the concept. But while we're on the topic: On further web-searching, I noticed that the Jargon File's entry on Open Source does not currently contain any attribution to Christine. It probably should. I thought I'd bring it to your attention so you can update the entry. It's the meritocratic thing to do. :-)
>On further web-searching, I noticed that the Jargon File's entry on Open Source does not currently contain any attribution to Christine.
That's because it doesn't attribute anybody. Chris understands why this is; she gets it about victory happens when your ideas are such conventional wisdom that your name isn't on them anymore.
Datapoint: Until five minutes ago I thought it was coined by Eric. Thanks for correcting my brain.
I still have the impression that ESR popularized the term. Wouldn't be surprised if people conflate the two — I figure that's probably what happened to me.
>I still have the impression that ESR popularized the term. Wouldn't be surprised if people conflate the two — I figure that's probably what happened to me.
You have that impression because in fact I did popularize the term. And that conflation does occur.
random832 >Why does it not being his fault equate to it not being a problem?
I didn't say it equates to that, and I do think it's a problem. It's just not a problem with meritocracy. Quite the opposite: it's a problem with a lack of meritocracy.
esr> That's because it doesn't attribute anybody.
That's a fair point.
The problem is, they think their proposed policies will do a better job of approximating a real meritocracy…
I honestly don't understand why you bother to indulge in overly generous speculation on their thought processes, when the plain text of the front page at contributor-covenant.org says:
[other stuff] and side effects of the pervasive cult of meritocracy make contributing to open source a daunting prospect for many people.
This isn't that hard to parse. They aren't complaining that the goal of meritocracy hasn't been fully reached, or that it needs some tweaking — they are complaining that it is pervasive and has pernicious side effects. Later text at that URL makes it clear that one of the ways to fix this is by "welcoming all people to contribute."
Even if if you accept this as a naive worldview, the text of the actual covenant puts immediate lie to it:
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they
deem inappropriate, threatening, offensive, or harmful.
> But, in reality, the SJWs are completely full of shit about this. There is a reality here; it's not just conflicting narratives all the way down.
Are you saying that it is impossible to have an unconscious bias about someone based on their race/gender/etc? Or that hackers are, every single one, immune to this?
It doesn't even have to be racism, or any -ism. A bias against "outsiders" [i]in general[/i] could reasonably be said to disproportionately affect minorities if "insiders" tend to be white/male/english-speaking/etc.
Even if they're mistaken about this, why can't they just be [i]honestly mistaken[/i] rather than you interpreting everything as some sort of pseudo-marxist deliberate sabotage?
Also, incidentally…
> It has been suggested that djangoconcardiff might be a troll … The problem with this idea is that no SJW disclaimed him – more generally, that "Social Justice" has reached a sort of Poe's Law singularity
SJWs don't seem to be so dense on the ground at github that any would even have [i]heard[/i] of this incident before it was already resolved. Certainly none showed up to comment before the project maintainer reported the post to github staff as harassment and got it deleted (and yet in your post you imply it's a big damn mystery how and why it got deleted). At which point any effort to disclaim him "doesn't count" as anything more than "it has been suggested that he might be a troll".
>Are you saying that it is impossible to have an unconscious bias about someone based on their race/gender/etc? Or that hackers are, every single one, immune to this?
I'm saying that in more than 30 years of closely observing the hacker community I have seen no credible evidence of such bias, and that there are excellent reasons to doubt that such "unconscious bias", to whatever extent it exists, affects behavior in any way above measurement noise.
>A bias against "outsiders" [i]in general[/i] could reasonably be said to disproportionately affect minorities if "insiders" tend to be white/male/english-speaking/etc.
Supposing this were true, it would not a warrant to yell "racism" or "sexism", because the bias is not racial or sexual.
>Even if they're mistaken about this, why can't they just be [i]honestly mistaken[/i] rather than you interpreting everything as some sort of pseudo-marxist deliberate sabotage?
Because their presuppositions, rhetoric, and tactics are precisely those of volk-Marxist sabotage, with djangocconcardiff as a perfect example. I can't really blame you for being ignorant of Marxist theory and rhetoric, but I am not ignorant and I know the shit by its stink.
> they are complaining that it is pervasive and has pernicious side effects.
It is absolutely clear to me that what they mean by "cult of meritocracy" is not what you are claiming it means.
> Even if if you accept this as a naive worldview, the text of the actual covenant puts immediate lie to it:
I have no idea how you think the text you quoted contradicts any of my theories.
@Random832: what they mean by "cult of meritocracy" is not what you are claiming it means.
To me, "meritocracy", in the context of a technical project, means that, if you want to contribute, your contribution gets judged on technical merit, and nothing else. So a truly meritocratic Code of Conduct would just be that one sentence. Even if you don't think that's realizable in practice, it should at least serve as a useful idealized model.
Given that, it seems to me that the proposed SJW Code of Conduct is a lot farther from that idealized model than, for example, the one Erbo posted in this thread.
And I realize I use some pretty offensive language in my Erbosoft Code of Conduct, but, as the saying goes, "You can get more with a kind word and a blunt instrument than you can with just a kind word." My code of conduct is a blunt instrument. :-)
Besides, I suspect that the set of people that would be offended by the profanity and the set of people that are intended to be deterred by such a Code of Conduct have substantial overlap.
> Supposing this were true, it would not a warrant to yell "racism" or "sexism", because the bias is not racial or sexual.
There is, however, a difference between "yelling "racism" or "sexism"" vs declaring something to be a problem, even to be a problem because of the effect on minorities/women.
> "with djangocconcardiff as a perfect example"
And how convenient for the narrative that you either don't believe he is, or don't believe it matters if he is, a troll. Incidentally, that line of argument reminds me nothing so much as "We should still treat ${fallen-apart accusation of rape or abuse which has got egg on the media and feminists' face} as if it is true anyway, because it stands in for all the other equally heinous cases [I have in my hand a list] that really are."
And even if it precisely matches, you haven't provided any reason not to believe that it's "useful idiots all the way down" – or in other words what you call a "prospiracy" – which does not justify the moral outrage against individual "members" that you are arguing for.
> To me, "meritocracy", in the context of a technical project, means that, if you want to contribute, your contribution gets judged on technical merit, and nothing else.
But they didn't say "meritocracy", they said "cult of meritocracy".
> Given that, it seems to me that the proposed SJW Code of Conduct is a lot farther from that idealized model than, for example, the one Erbo posted in this thread.
I really don't understand why. Patrick Maupin pointed out "Later text at that URL makes it clear that one of the ways to fix this is by "welcoming all people to contribute."" but I honestly don't understand why this is the case, unless you deliberately misinterpret it as requiring all contributions to be accepted regardless of quality.
Random832:
> But they didn't say "meritocracy", they said "cult of meritocracy".
Even with all the disparagement I can find to put on the word cult (and that's a lot), this is a cult I am a proud member of. OTOH, if (as you seem to propose) they are arguing for meritocracy but against some sham version of it, they bloody well should say so. We aren't in Wonderland, and words mean what they mean.
The fact that the only thing they have to say about merit is disparaging speaks volumes. The fact that you're still arguing what you're arguing speaks even more volumes.
welcoming all people to contribute."" but I honestly don't understand why this is the case, unless you deliberately misinterpret it as requiring all contributions to be accepted regardless of quality.
I was comparing and contrasting "welcoming all people to contribute" with the actual text of the covenant, which spells out all the people they don't welcome contributions from, and hint — quality has NOTHING to do with why they say they should reject stuff.
The most charitable reading of the Code of Conduct itself places it orthogonal to any code quality concerns, but the text at the website that only mentions merit in the disparaging phrase "cult of meritocracy" and then goes on to say we need to welcome all contributions obviously places code quality second, if at all.
The code itself then makes it clear that contributions should be rejected if they come from the wrong source, whether they are meritorious or not. This doesn't square with your lame interpretation that of course they don't mean all comers, because they are going to reject bad quality code.
No, a plain reading of the covenant is that they don't mean all comers because they are going to reject code from people who make them cry.
And, finally, esr said:
Because their presuppositions, rhetoric, and tactics are precisely those of volk-Marxist sabotage,
which is true, but you don't need to go there. All you have to do is not follow them down the rabbit hole, and take the actual words at that site at face value, and realize that they don't add up to anything good.
> The code itself then makes it clear that contributions should be rejected if they come from the wrong source, whether they are meritorious or not.
Wait. Are you suggesting that no open-source project should ever "ban" (i.e. deny access to discussion venues, patch submission mechanisms) anyone for any reason?
@ Erbo
If you're an asshole, you're banned from the project. Permanently.
What if, a month later, the asshole submits a valuable patch that you would accept if it came from anyone else. Do you accept the patch?
I think it's important (and this is a failure on the COCs' part as much as anything) to distinguish between being able to contribute code vs being a "member" of the project or being allowed to hang out in the project's space.
Maybe projects should be willing to ban people for misbehavior so that everyone else doesn't have to hang around them, but still provide an alternate way for them to contribute patches and bug reports (maybe an email address of a designated thick-skinned co-maintainer?)
@ Random832
…to distinguish between being able to contribute code vs being a "member" of the project or being allowed to hang out in the project's space.
I am expecting Erbo to make this point, and then I go: "Right. That's a meritocracy.
@Random832: they didn't say "meritocracy", they said "cult of meritocracy".
But they don't give any non-cult version of meritocracy–they don't talk about merit at all. So anyone who puts value on technical merit is SOL with their Code of Conduct, as far as I can see.
I really don't understand why.
Because they don't freakin' talk about merit at all. Which makes it clear that they don't actually give a crap about merit; it's just the same old chimp power game.
> Wait. Are you suggesting that no open-source project should ever "ban"
Not at all. Which IMO makes it laughable or naive to say up front they will be "welcoming all people to contribute, and pledging in return to value them as human beings…"
The text of the code itself shows they recognize they can't do that, so you can remove naive, and laughable remains.
> Because they don't freakin' talk about merit at all.
No, it's worse than that. It would certainly be possible to arrange a code of conduct to be orthogonal to contribution merit, e.g. "we try to be respectful when giving criticism." But they have gone out of their way to assert that this code of conduct is in place of, not an adjunct to, any culture that cares about merit.
@Patrick Maupin – have you considered the possibility that their opposition to the "meritocracy" argument may have been more directed towards giving established contributors a pass on bad social behavior on due to the "merit" of their past contributions, than anything against rejecting low-quality contributions?
I also don't see how it is necessarily anti-meritocracy to remove people from official discussion venues or tell them not to describe themselves as core contributors, as long as they're not prevented from submitting patches. They might be discouraged from contributing, but we've already established that only real contributions matter, not hypothetical ones.
By the way, I looked it up in a dictionary… meritocracy means rule by people selected on the basis of ability, it doesn't mean a system of valuing technical contributions by the merit of the code (and I have no idea why, from start to here, we've all been treating it as if that's its primary or only meaning). So if anything, their "cult of meritocracy" refers to the idea that people are being given some sort of untouchable status based on them being 'people of merit', rather than anything regarding how code is accepted or rejected.
Which, I think, is strong evidence that djangoconcardiff is a troll – because his language was calculated to frame the debate as being about code instead of people.
@Random832: meritocracy means rule by people selected on the basis of ability, it doesn't mean a system of valuing technical contributions by the merit of the code
But the one requires the other; if you're going to select people on the basis of ability, you have to judge everyone's technical contributions on technical merit, and nothing else. So if you have a Code of Conduct that says nothing about judging contributions solely on technical merit (or worse, actively works against that), how can it possibly help build a meritocracy?
@Peter Donis: You've completely missed my point. Selecting people to have a status where they can do no wrong, because you're terrified to take away that status because they might contribute less, is not a good thing, regardless of whether it's on the basis of ability or otherwise.
And no-one has advanced any argument that actually supports "meritocracy" in the form of rewarding people for past contributions with things like "core contributor" titles and de facto immunity from being kicked off the mailing lists or whatever. They can still contribute without those things. And if they choose not to, either out of spite or due to frictional costs, they're not any different from any potential contributor who's been run off by the LKML culture or whatever.
their "cult of meritocracy" refers to the idea that people are being given some sort of untouchable status based on them being 'people of merit', rather than anything regarding how code is accepted or rejected.
I don't see this going on at all. All the complaints about Linus Torvalds, for example, are entirely about how he accepts or rejects code. Nobody complains that he's not nice to them at parties. They complain that he lays into them when they submit a patch that is technically stupid.
(What makes it even worse is that, at least in every case I've seen, the patch was technically stupid–one example I recall was about someone submitting a patch that broke userspace, and then, when Linus said "you never f**king break userspace", or something like that, instead of saying "you're right, I screwed up", they tried to argue that it was ok to break userspace in that particular case. Even if, hypothetically, that argument was not completely out to lunch, it's an argument that should have been made before submitting the patch–indeed, before even embarking on the work at all.)
> So if you have a Code of Conduct that says nothing about judging contributions solely on technical merit (or worse, actively works against that), how can it possibly help build a meritocracy?
You can judge contributions solely on technical merit without judging contributors solely on technical merit. And if the former is what you mean by meritocracy, and the latter is what the SJWs think it means, then there's really no conflict.
> I don't see this going on at all. All the complaints about Linus Torvalds, for example, are entirely about how he accepts or rejects code.
Well, technically speaking, they're about what he writes to the mailing list after rejecting code. "How he accepts or rejects code" suggests, wrongly, that they're about how he decides what code to accept or reject. The difference is that one of these things is technical and the other is not.
@Random832: Wait. Are you suggesting that no open-source project should ever "ban" (i.e. deny access to discussion venues, patch submission mechanisms) anyone for any reason?
Interesting question. Let's do a little thought experiment (and gleefully break Godwin's Law in the process.) Do we accept code from Hitler? Or Pol Pot? Or Stalin? Hitler likes your project, he contributes decent-or-better code, he keeps his politics off the mailing list, and even refrains from sending the SS to kill your Jewish contributors. He sticks to purely technical issues the entire time he's part of the project… maybe it's a hobby, something to do when the tensions of running the Third Reich get to be too much. Everyone needs a hobby.
If the answer is "No," then we've accepted the principle that there are some people we just don't want around, and it's OK to keep them off the project. Now we simply need to figure out who those people are… and I don't have a problem with that as long as the criteria for rejection is at least vaguely fair.
If we answer "Yes," then we've got a real, true-blue meritocracy! Yay! (I think.) Personally, I'd prefer to contribute to a project that doesn't involve Hitler and I suspect that even the most hard-core meritocrats among us feel the same way – some people are just beyond the pale.
I suspect that answer is someplace in the middle – I don't think anyone wants code from Hitler, however divorced from politics it might be. On the other hand, merit counts for something, particular where lives are involved, as with GPS, so I don't think most of us want to arbitrarily ban folks based on their race or genital-touching preferences – that person who's religious preferences we dislike might write awesome code.
So we're left with banning the assholes. Are we done now?
I think another, related issue is…
Let's suppose, for a minute, that there are some aspects of the "sexism" argument that are true. Not that anyone hates women or is against women contributing, but that there are some aspects of, say, LKML culture that are, for whatever reason (whether it's because of how people are socialized differently, or biological differences, or whatever other reason, it doesn't matter), more off-putting on average to women than to men.
I'm not sure of it, myself, but let's assume for the sake of this line of thought that it's true.
The problem is, even if it is true… it's nobody's fault. Well, "society", maybe. But certainly no-one present, not in anything remotely resembling a direct way. No-one involved is, personally, to blame. And because of that, no-one takes any responsibility to fix it. Imagine if we had that attitude towards buffer overruns.
> I suspect that answer is someplace in the middle – I don't think anyone wants code from Hitler, however divorced from politics it might be.
The trouble is that Esr has denounced me as even worse than Hitler, or something along those lines – but I am pretty sure it would go against his principles to reject my code contributions on the basis of our political disagreements.
Indeed, as the left moves ever leftwards, I am pretty sure that all of us, including Obama had worse than Hitler political positions ten or twenty years ago. In an earlier discussion, esr attributed political positions to his parents and his past self that seem extraordinarily enlightened for those times. We have always been at war with EastAsia.
Consider what is happening in Sweden now, as the Swedish ruling party, overwhelmed by a flood of "asylum seekers" is forced to furtively adopt policies that everyone in Sweden, all decent correct thinking people a month or so ago, agreed were much worse than Hitler. In the current environment, being opposed to people that are worse than Hitler is likely to result in you being opposed to a quite inconveniently large number of people.
The "cult of meritocracy" in hacker culture « Quotulatiousness
@flaviusb please read this, the best succint article about human motivation I've ever read: http://lesswrong.com/lw/uh/trying_to_try/
TL;DR if meritocracy means you only respect actual success no matter how unfair is (success by the genetically gifted, rich parents, whatever) you have to have it, because when you try to detect and reward trying hard and failing, people will naturally ease into "trying to try" i.e. pretending trying. And it is not even just a cynical thing to run on others, it is actually a self-help method how to configure your self-talk to be productive yourself.
@JAD
"to furtively adopt policies that everyone in Sweden, all decent correct thinking people a month or so ago, agreed were much worse than Hitler."
In countries where people still have a living memory of the rule of the Nazi's (and Sweden is close enough), the phrase "worse than Hitler" is never used. Claiming any US politician has such ideas shows you really do not know what you are talking about.
But we already knew you do not know what you are talking about.
@TheDividualist
"TL;DR if meritocracy means you only respect actual success no matter how unfair is (success by the genetically gifted, rich parents, whatever) you have to have it, because when you try to detect and reward trying hard and failing, people will naturally ease into "trying to try" i.e. pretending trying."
A meritocracy is the "rule of the successful contributors".
First, there is a large difference between "Rule" and "Reward". Those who rule because they contributed most can very well decide to reward the spoils based on effort (trying). The reason is that to get a single success, you need many failures.
Only rewarding the success is unfair, but giving the ruling power to those who fail is madness.
In Open Source it is clear that we want those who can improve the project most to "rule", but we also want to reward those who do the menial work and those who honestly try but fail.
And that is exactly what most project leaders try to communicate: Doing useful work, any useful work, is really appreciated, be it moderating forums or writing documentation and tutorials.
> In countries where people still have a living memory of the rule of the Nazi's (and Sweden is close enough), the phrase "worse than Hitler" is never used.
The Swedish democrats are supposedly Nazis, according to the Social Democrats. Why are they Nazis? For advocating pretty much what the ruling Swedish parties, overwhelmed by the massive inflow of illegals, now find themselves doing
Tell that to Antifa, the state sponsored thugs that go around beating up dissidents. Everyone they beat up is worse than Hitler.
"Everyone they beat up is worse than Hitler."
Please give us references of who are actually use the words: "Worse than Hitler". I have never seen this printed, except in your comments. So I am curious who uses them. Pointing to Antifa is not the same.
"Tell that to Antifa, the state sponsored thugs that go around beating up dissidents."
I would like to know how the "state-sponsored" part is determined?
They are not meritocrats, they are communists.
Meritocrats believe that people have different talents, temperaments and interests, something for which there is overwhelmingly massive evidence, and want to match these as best as possible to important tasks so as to best serve human welfare.
Communists start from the totally arbitrary assumption that every person (or at least group, to make it sound a bit less bald-faced ludicrous) starts with the same talents, temperament and interests, and any deviation from this is due to a massive evil conspiracy. That's really the only conclusion left once you have excluded "our assumption is horribly mistaken" as a possibility.
The communists do believe that in the status quo talents are mismatched to tasks, because they believe there is no such thing as a difference in talent while they see persistent patterns in how people are assigned to tasks. If some people or groups seem to be doing consistently better than others it must be because they are evil parasites.
It's not even worse than Hitler, it's just the same basic logic, neither better nor worse.
James May on 2015-11-17 at 07:47:25 said:
I'm not sure what's so complicated about a meritocracy. A bridge doesn't know or care who built it. If you think it does it's liable to fall down. Why be surprised people who hate the idea of a meritocracy are the fallen?
> A bridge doesn't know or care who built it.
It also doesn't care whether the builder is given a position of power as a reward for having built it.
dave taht on 2015-11-17 at 10:14:37 said:
Whatever happened to "I despise everything you just said, but will fight to the death for your right to say it, {brother, sister}?
>Whatever happened to "I despise everything you just said, but will fight to the death for your right to say it, {brother, sister}?
See, this is where being able to recognize SJW ideology as a kind of volk-Marxism is helpful. Once you have, you'd no more expect it to defend free speech than you'd expect an SS Gruppenfuhrer to say the kaddish.
random832> Are you saying that it is impossible to have an unconscious bias about someone based on their race/gender/etc? Or that hackers are, every single one, immune to this?
None that a boilerplate "code of conduct" can correct. If you have an unconscious bias based on X, you won't change your behavior in response to the commandment that "thou shall not discriminate based on X". That's because the bias is unconscious, so to your mind you're not discriminating by X in the first place. (Disclaimer: I don't speak for hackers because I'm not one mysefl. But my point applies to humans in generals, and to that I can speak.)
I also don't see how it is necessarily anti-meritocracy to remove people from official discussion venues or tell them not to describe themselves as core contributors, as long as they're not prevented from submitting patches.
There are bad actors, and any group that wants to survive will have a formal or informal method of insulating itself from them. But the code gives lots of wiggle room for doing political stuff under the cover of being nice. The second part of your argument — the answer to speech is certainly more speech, and you are always free to ask someone not to describe themselves in a way that you feel is inaccurate. But if someone decides to keep describing themselves as a core contributor, what are you going to do about it? What do you think should happen?
They might be discouraged from contributing, but we've already established that only real contributions matter, not hypothetical ones.
Perhaps you didn't mean it this way, but this is the best argument so far against the code of conduct. Its entire rationale, as discussed in the first two paragraphs on its home page is premised on the hypothetical contributions that might materialize once it is adopted.
> Perhaps you didn't mean it this way, but this is the best argument so far against the code of conduct.
I was pointing out the absurdity in giving a damn about the possibility that someone who you "ban" might stop contributing when the entire argument relies on their hypothetical future contributions. And without that, your argument falls apart.
In other words, you're clearly unable to grasp sarcasm, since I was pointing out the idea that people being discouraged doesn't matter as a problem in your argument, not uncritically endorsing it.
@Brian Marshall: "What if, a month later, the asshole submits a valuable patch that you would accept if it came from anyone else. Do you accept the patch?"
Ideally, I never see the patch at all, because I have used technical means to block the asshole from the project. (Think Facebook "block." Can you do that on GitHub?)
Anyway, the chances that someone branded an "asshole" under the ECoC will even have the capability to submit a worthwhile patch are minimal, given that one of the roads to assholedom is whining about a rejected patch. Not merely "getting a patch rejected." The appropriate response to having a patch rejected is to debate it on its technical merits and either abandon the effort or revise the patch. It's the "oh, you aren't accepting my patch because you're biased against Latina bisexual transwomen!" response that is the mark of the asshole….and someone who has to resort to those arguments is unlikely to have the technical chops to back themselves up.
michel v on 2015-11-17 at 10:59:29 said:
The only thing worse than your pathetic fall into irrelevance, is that there may be young hackers who read your posts and think you represent "hacker culture."
>The only thing worse than your pathetic fall into irrelevance, is that there may be young hackers who read your posts and think you represent "hacker culture."
I truly, deeply love comments like these. That is, people who scream that I'm falling into irrelevance not realizing that their felt need to do so conforms the exact opposite.
> given that one of the roads to assholedom is whining about a rejected patch
Yes, but he was talking about the other roads. If there are any.
If I didn't recognize the sarcasm, it's because the first part of your argument is against a position you seem to feel I have taken that I have never defended, e.g. a strawman.
IMO, any group should feel free to adopt this CoC or not, and/or to expel anybody for any reason or no reason whatsoever.
But personally, I would be leery of investing time and energy in any group which has carefully considered the history and meaning of the CoC and then decides to adopt it anyway. I'd much rather be around others who likewise have no use for the thought police.
> Yes, but he was talking about the other roads. If there are any.
There are certainly people who are extremely competent but are difficult to deal with. This is something that is best dealt with on a case-by-case, project-by-project basis. Attempting to prescribe behavior for all interactions in a sphere (and even dragging in ex parte interactions) is, as esr has pointed out, the hallmark of those who wish for a centralized command-and-control economy.
> That is, people who scream that I'm falling into irrelevance not realizing that their felt need to do so conforms the exact opposite.
Without implying a conclusion either way, the minimum level of relevance necessary for people to want to complain about someone on the Internet is far below the level of relevance you claim to have. Maybe even below the lowest level of relevance your worst critics have accused you of having.
Tom Hunt on 2015-11-17 at 13:23:38 said:
> Interesting question. Let's do a little thought experiment (and gleefully break Godwin's Law in the process.) Do we accept code from Hitler?
Personally, granting your premises regarding his behavior, I'd more or less without complaint accept his code. (Or substitute Stalin, or Pol Pot, or someone else; the comparison to Hitler has been used too much, and by the wrong kind of people, to generate much of a revulsion reaction in me anymore.)
The greater danger you run into in such a case is that of entryism (and this is where it profits one to substitute the name of someone they actually despise personally, not just an abstract symbol of Evil; the visceral reaction is greater). That is, that by establishing credit within the community on the basis of their code (granting it's genuinely meritorious), $DESPISED_PERSON may be laying a foundation to later use that respect to promote their despised agenda. In the general case, it seems this is a very real threat; see the projects which actually do pay credence to this Code of Conduct nonsense. (And this is why it's better to substitute the name of some modern enemy, rather than Hitler literally; the risk of a project takeover by entryist neo-Nazis is low, to say the least, and so using Hitler himself risks overlooking this risk.) Whether a contributor should be banned on the basis of potential entryism, rather than mere odiousness, seems a matter of an individual project lead's preference and risk-tolerance. But it's by no means clear to me that the answer is always "ban them".
>I truly, deeply love comments like these. That is, people who scream that I'm falling into irrelevance not realizing that their felt need to do so conforms the exact opposite.
It's interesting, too, that this is always the insult the drive-by flamers use. They don't even bother denouncing you for your putative thoughtcrime; they merely declare you to be irrelevant. Presumably because "omg, are there still people like this in 2015? Wow, just wow".
As everyone knows, the wave of the future is leftism, and anyone who dissents is an outdated relic.
> Presumably because "omg, are there still people like this in 2015? Wow, just wow".
I really don't think the suggestion that he's irrelevant has much to do with his views, except that it is in speaking out about those views that it's most likely to come up [because he says he speaks for all hackers and that all (or a solid majority of) hackers share those views]
Meanwhile, it's undeniable that his profile is much lower than it once was. Has he made the mainstream news since the Halloween Documents? It's been a decade since he's published any books. For people to whom any of those is a primary measure of "relevance", he's certainly less relevant than he used to be, if not irrelevant, and his attitude has not changed to match.
>Meanwhile, it's undeniable that his profile is much lower than it once was.
I certainly intended that outcome.
On the other hand, the reaction when I show up at a live event like FOSSCON 2015 is, from a certain angle, entertaining. I generally try to delay having people figure out who I am as long as I can, because I know jaws are gonna drop and fanboys are gonna fanboy once the penny drops. This somewhat impedes my ability to have actual conversations.
Same thing when I visit an IRC channel I don't frequent. Only it's funnier there because one of the common reactions is "Prove you're the real ESR!" At which point I'm likely to say something like "You've found me out. I am, in fact a mere simulation of ESR running on a darknet supercomputer buried beneath the Transylvanian Alps," … and someone else will say "Yeah, that's him."
But ultimately, at this point it's going to be tested. He's made a [metaphorical] call to arms; his relevancy can be measured by who answers it.
The Monster on 2015-11-17 at 13:59:16 said:
> Let's do a little thought experiment (and gleefully break Godwin's Law in the process.) Do we accept code from Hitler?
No, that's not breaking Godwin's Law. It's COMPLYING with it.
Godwin's Law simply states that the longer a discussion continues, the closer the probability of someone bringing up Hitler or Nazis gets to 1. Contrary to popular opinion, it does not in any way cast aspersions on the first person to do so, including but not limited to "you said 'Hitler', so you lose!".
@ Michel v
I assume that you intended your one sentence opinion as some sort of insult or perhaps as a warning to others on this board. If the latter, then you may wish to establish some credibility first by making an intelligent comment. The unintelligent do not tend to stick around in this place for very long.
The Monster> Do we accept code from Hitler?
If it's good code, sure why not? Come to think of it, maybe you should accept it even if it's lousy code. Every hour he spends coding is an hour he's doesn't work on evil, destructive projects.
Oops, that quote was from troutwaxer, not The Monster. Sorry for the misattribution!
troutwaxer> If we answer "Yes [to Hitler's patch]," then we've got a real, true-blue meritocracy! Yay! (I think.) Personally, I'd prefer to contribute to a project that doesn't involve Hitler and I suspect that even the most hard-core meritocrats among us feel the same way – some people are just beyond the pale.
No problem. Feel free to contribute to a different project instead. The problem in cases like 'djangoconcardiff"s arises when somebody moves from "I don't want to contribute to a project like that" straight to "YOU shouldn't be allowed to RUN a project like that. And if you do, I'll report you to the authorities."
It must go without saying (at least it doesn't seem to have been noted in comments here) that (successful) project leaders actually do more work than admit code contributions.
Whenever more than one person is collaborating on a project there will be interpersonal dynamics at play. A successful project leader has a role in managing the effects of those social interactions as well as the technical merits of code submissions.
There must be *personality* involved, otherwise any project leader would be immediately fungible (without interruption to the project) for another identity, which we know is not the way leadership transitions commonly pan out.
Is it possible that those of you who seem to honestly believe that there is no place in software development for principles that call for people to be reasonable in their personal interactions might be simply under-estimating the importance of these interactions for overall project success?
@Random832: technically speaking, they're about what he writes to the mailing list after rejecting code.
If you do something technically stupid, and Linus calls you on it, then you don't complain about the words he used. You fix what you did so it's no longer technically stupid.
If someone else does something technically stupid, and Linus calls them on it, and instead of fixing it, they make lame arguments about how it wasn't really technically stupid in that particular case, you don't complain about the words Linus used, and you certainly don't say that the person who did the technically stupid thing is being "discriminated" against. If you aren't willing to say out loud that yes, what the person did was technically stupid and their argument when called on it was lame, then you should just keep silent. Complaining about the words Linus used doesn't help the technical issue, it hurts it, by distracting attention from where it belongs.
one of these things is technical and the other is not.
No, they're both technical, because, as above, if you focus on the words Linus used instead of the content of what he said, you're distracting attention from the valid technical issue.
Perhaps the problem here is that you and I have different priorities. I think that, for a project like the Linux kernel, fixing technical issues, or even better avoiding them in the first place, takes precedence over managing people's feelings. You appear to think the opposite. In itself that's fine; reasonable people can disagree. But my response to the disagreement is, fine, fork the project so you can have your own version that you manage the way you want to manage it, and leave Linus alone to manage his version the way he wants to manage it. The SJW response to the disagreement, which you appear to support, is to impose martial law on all projects and force them to conform to their Code of Conduct. True, they can't actually do that, at least not yet, but that's what they would like to do, and failing that, they at least want to pester the hell out of every project with any public visibility whatsoever and make the maintainers' lives a burden to them for no good reason. That is unacceptable.
@Random832: It also doesn't care whether the builder is given a position of power as a reward for having built it.
Nobody "gave" Linus his position of power in the Linux kernel. He started it, fer chrissake. It's his project.
This looks to me like just another version of the "daddy model" of wealth; in this model, no wealth is ever created, it can only be doled out by some higher omnipotent entity. But in the real world, wealth is created, and so are "positions of power" like the one Linus holds for the Linux kernel. Nobody doles them out as rewards for good behavior; they are created out of nothing by people building things of value. The failure to recognize this is, as esr has already pointed out several times now, a huge red flag of Marxist memes lurking in the background.
> my response to the disagreement
I should have said "the hacker response to the disagreement, which I support", since plenty of others in this thread have already stated it.
>Complaining about the words Linus used doesn't help the technical issue, it hurts it, by distracting attention from where it belongs.
So there's an finite unchanging supply of attention, and absolutely none of it can be spared for considering the possible future benefits of changing how interpersonal interactions work?
If you really want to avoid distraction, why not just back the patch out and move on, and temp-ban the person who submitted it for a month for wasting everyone's time? Practical problem solving rather than a lot of noise.
> Nobody "gave" Linus his position of power in the Linux kernel. He started it, fer chrissake. It's his project.
I was talking in an abstract sense, and the example was meant to map more closely to Elia (who seems to have been a subordinate to "meh") in the Opal thing anyway
> But in the real world, wealth is created, and so are "positions of power" like the one Linus holds for the Linux kernel. Nobody doles them out as rewards for good behavior; they are created out of nothing by people building things of value
"positions of power" in open source projects are not created and held as property, they are a continuous process of the wider community's decision to continue working with that person rather than forking the project.
@Random832: "Yes, but he was talking about the other roads. If there are any."
The other currently-defined roles in the ECoC are (a) bitching about my rejection of the OPEN CoC and similar CoCs, and (b) trying to force me to change the ECoC in ways that are offensive to me. In both cases, this implies that the potential asshole is focused more on the project's CoC than on any technical issues, indicative of SJW status and thus assholedom.
Bear in mind that, under most circumstances, nobody should give a shit about the ECoC at all. They should just contribute, focus on technical issues, and do their thing. No different from how a dev team at a company would function.
@Patrick Maupin: "There are certainly people who are extremely competent but are difficult to deal with. This is something that is best dealt with on a case-by-case, project-by-project basis. Attempting to prescribe behavior for all interactions in a sphere (and even dragging in ex parte interactions) is, as esr has pointed out, the hallmark of those who wish for a centralized command-and-control economy."
This is true. I don't think it's possible for me to define in advance every possible way in which a person can become an asshole. Assholes are so ingenious. :-) My blog's comment policy is in a similar spirit:
"There may be free speech, but there is no free lunch. You want to make a speech, get your own blog; I run and pay for this one. I reserve the right, at all times, to delete any comment if I choose not to want it here."
And I took great pains to make it clear in my post that an environment of general hostility that drives people away is not the same thing as an individual "villain" "discriminating against" an individual "victim", but that doesn't mean it's not a problem, so I'm very annoyed right now that you once again characterized this as a question of whether people are "being "discriminated" against".
@Random832: So there's an finite unchanging supply of attention
It's certainly harder to create more of it than it is to create more of a lot of other forms of wealth. :-)
If you really want to avoid distraction, why not just back the patch out and move on, and temp-ban the person who submitted it for a month for wasting everyone's time?
In the particular example I was thinking of (breaking userspace), IIRC Linus' first response was basically to revert the patch, say "we never f**king break userspace", and leave it at that. It was only when the submitter tried to argue that it was OK to break userspace in this particular case that there were fireworks.
As for temp bans over cursing as a way of getting the message across, I don't know enough about the details of kernel development to know for sure, but I'm thinking it wouldn't be practical, since anyone who is submitting patches to Linus is already aggregating the work of many other people, so temp banning them would cause a huge blockage in the pipeline.
Yes–so why create a huge hoohah to impose a Code of Conduct, instead of just forking if you're not happy about how someone is managing a project and repeated requests to change have failed?
In other words, you have just stated that the community already has a process in place to handle this issue; yet you advocate imposing a Code of Conduct on projects instead of letting that process work. Why?
> I really don't think the suggestion that he's irrelevant has much to do with his views, except that it is in speaking out about those views that it's most likely to come up [because he says he speaks for all hackers and that all (or a solid majority of) hackers share those views]
I've seen the same insult ("you're irrelevant, you're outdated, not in touch with the wave of the future, history is leaving you behind") in manymany contexts unrelated to ESR or his actual, objective relevance. Invariably, it's a leftist or an SJW directing it at someone who opposes leftism. (Interestingly enough, "you're irrelevant" tends to be directed at those who openly place themselves in opposition to SJWism, like ESR or Vox Day; the reaction to someone who criticizes any individual piece of SJW batshittery, while not explicitly opposing the movement as a whole, is much more "how dare you thoughtcrime like that, you thoughtcriminal!" A tactical move?)
> an environment of general hostility that drives people away is not the same thing as an individual "villain" "discriminating against" an individual "victim", but that doesn't mean it's not a problem,
I think how much of a problem it is depends greatly on against whom the general hostility is directed. Linus' habits may well create an environment of general hostility against those who submit bad patches, but I'm more or less fine with that. (Meanwhile, it's classic SJW entry tactics to present any hostility from anywhere directed at anyone as an "environment of general hostility" directed against whomever they've decided is disprivileged this time.)
You know, as an aside… the "never break userspace" policy or equivalent actually seems like a very unique position (well, apart from MS Windows). Certainly we wouldn't have much compiler optimization if everyone were afraid of breaking programs that rely on a particular outcome of undefined behavior. Programs other than the kernel can have bugs, and pulseaudio may well have had one, and it's really not Linus's place to say it didn't and characterize it as "blaming" the program, since Pulseaudio is not his project. Being perfectly backwards compatible even to programs that have bugs may or may not be a laudable goal; it clearly is one of the Linux Kernel's actual goals in light of this… but it's not the only possible sane position to hold.
> (Meanwhile, it's classic SJW entry tactics to present any hostility from anywhere directed at anyone as an "environment of general hostility" directed against whomever they've decided is disprivileged this time.)
As far as I know the contention is that women are less able to deal with it (and thus would be more able to participate in the project if it weren't there), rather than that it's directed at them specifically.
You're still transforming this into something that has to be someone's fault, where someone has to be doing something wrong for there to be a problem. And therefore nothing that someone can't be blamed for is a problem worth fixing. And you're projecting that onto the people pointing out the problem and accusing them of accusing others of "discrimination" or other wrongdoing.
failing [to impose martial law], they at least want to pester the hell out of every project with any public visibility whatsoever and make the maintainers' lives a burden to them for no good reason.
Where "a burden" extends to trying contacting his employer and employer's clients in this case: https://mail.python.org/pipermail/python-cuba/2015-July/000106.html And as we've seen in others, ending his career (when it comes to programming it's almost always, if not always a male being targeted). These people are profoundly evil, to attack so severely for slights so minor or non-existent except in their fevered minds.
> You're still transforming this into something that has to be someone's fault, where someone has to be doing something wrong for there to be a problem.
I entirely acknowledge that a bad situation for which nobody is particularly to blame can still be a problem. It's also entirely possible that highly-acerbic norms in technical discussion fora might be one of those problems.
However, it is transparently obvious to me that the whole "code of conduct" initiative, pushed by SJWs supposedly in order to address the above (hypothetically a) problem, is in fact designed not with any technical objective in mind, but for the purpose of asserting and consolidating SJW political control of technical projects and communities. It is explicitly a goal of these people to kick everyone they define as a wrongthinker out of every community they can, to the extent of destroying communities which refuse to go along. Even granting the existence and seriousness of the 'general attitude of hostility', I cannot imagine it to be doing damage remotely comparable to what would result from consolidated SJW control. Thus, I oppose the whole thing, by means as vigorous as are available to me. Any similarly transformative proposition to address any supposed problem, if it is proposed by people who are visibly SJWs, I will likely similarly dismiss as a stalking horse.
@Random832: the "never break userspace" policy or equivalent actually seems like a very unique position (well, apart from MS Windows).
Linux and Windows, peas in a pod. :-)
it's not the only possible sane position to hold.
In the general case, I agree. But Linus has made his position for the Linux kernel so clear so many times that anyone who even thinks they might possibly, by some stretch, have an argument should know enough to try it out on him before they submit the patch, not after (or indeed, as I said earlier, before they even do the work at all). Pulseaudio is not Linus's project, true, but any project that runs on an OS has to be aware of how that OS expects projects to work with the kernel.
"You're still transforming this into something that has to be someone's fault, where someone has to be doing something wrong for there to be a problem. And therefore nothing that someone can't be blamed for is a problem worth fixing."
If nobody is doing anything wrong, how can there be "an environment of general hostility that drives people away"? Surely "the environment" can be unpacked to particular instances of hostility, for instance individual rebukes to bad patch submissions or the like.
If those rebukes cannot be proven to be specifically hostile to sensitive groups (women, gays, minorities, etc.), then I don't see that people in those groups claiming discrimination have a leg to stand on. I've participated on various boards and lists where it turned out the general culture was jackassery and so I left; but the jackassery was literally indiscriminate. Some folks dig that, some don't.
If your argument is "Women/gays/minorities can't handle jackassery and therefore it's discrimination" my answer can only be "Boo hoo. Grow up and join the real world."
> If your argument is "Women/gays/minorities can't handle jackassery and therefore it's discrimination"
See, now you're failing to unpack. (It's not my argument, but nevermind that for now) "…and therefore it's discrimination" is, as far as I can tell, entirely your invention. Something can be a problem without being a deliberate effort to alienate people. Why can't it just be "Women can't handle jackassery [ywnm] and that is one of several reasons why maybe it'd better to have less of it"?
What's the benefit of it, anyway, besides it evidently being too much of a distraction to think about not doing it.
> Why can't it just be "Women can't handle jackassery [ywnm] and that is one of several reasons why maybe it'd better to have less of it"?
Because "women can't handle jackassery" is an example of the sort of sexism that the majority of the hacker community doesn't want a bar of.
+1 for less jackassery, though.
grendelkhan on 2015-11-17 at 18:40:06 said:
Winter: Please give us references of who are actually use the words: "Worse than Hitler". I have never seen this printed, except in your comments. So I am curious who uses them. Pointing to Antifa is not the same.
Perhaps, in standard Jim style, he's taken a possibly-supportable claim and stretched it beyond recognizability? The whole Gamergate is worse than ISIS thing, maybe?
> Because "women can't handle jackassery" is an example of the sort of sexism that the majority of the hacker community doesn't want a bar of.
So the idea that statistical differences in ability between groups exist (regardless of the cause) is okay when it excuses differential outcomes, but not when it provides a reason to be accommodating of those differences?
+1 for less jackassery, indeed.
So let's say some project institutes a "no-jackasses" CoC*. Presumably the project owner is to enforce it. But the project owner is already in charge of setting the tone. If they choose to be a jackass anyway, or permit others to be jackasses, who is to enforce their CoC against them?
I don't see any way to force an owner (and by extension the group they lead) to stop being a jackass, at least not without unacceptable levels of coercion.
> I don't see any way to force an owner (and by extension the group they lead) to stop being a jackass, at least not without unacceptable levels of coercion.
No, and neither should there be. The appropriate response is to leave, and if you'd like, fork the project and found your own community more in line with your values.
(To clarify that, by all means *first* bring up the CoC violations with the owner and others first. Try to resolve things that way *before* taking the fairly drastic step of forking).
<snark>How 'bout: If women want the culture of a project to change to suit them better, it is discrimination against that culture – discrimination that should be stomped on! Ruin those women's lives!</snark>
I imagine that some projects could benefit from more participants that they could get if they seriously eased up on the jackassery.
OTOH, a project team might work together so well that maintaining the team is more important than attracting more people that don't like the current project culture.
Agreed, but the argument "jackassery is offputting to women, which is bad and should be fixed, but it's nobody's fault specifically" sounds like the desired solution is "it's really 'society' which should be fixed, but that's too hard, so we'll have to fix it one group at a time whether they like it or not." And then we get back to "who decides" again.
Right. The fact that open-source projects are run by a (hopefully benevolent) dictator is a good thing.
To steal a joke from P.J. O'Rourke…
Let the SJWs have their way, and sooner or later they will be pushing for mandatory helmets while taking a bath and legislated bedtime.
> So the idea that statistical differences in ability between groups exist (regardless of the cause) is okay when it excuses differential outcomes, but not when it provides a reason to be accommodating of those differences?
1) Statistical differences between groups are *never* justification for treating individuals differently based upon their group membership. This means one shouldn't presume that black people are thieves* because more black people are thieves in your society, just as one shouldn't preferentially hire black candidates because their group is under-represented in your field.
2) It is perfectly reasonable to be accommodating of the difficulties *individuals* may face. If someone is having difficulty with English**, be more patient and helpful than you might be with someone fluent in the language. If someone is new to coding in general, perhaps offer mentoring and more guidance with PRs than you might for a more experienced programmer.
3) There is no evidence (that I know of) that women are in some nebulous way "can't handle" jackassery, or are more sensitive to it than men. Even if there were, it still wouldn't alter the fact that treating *individual* men and women differently on that basis is sexist.
* http://www.abc.net.au/news/2015-11-12/melbourne-students-accuse-apple-store-of-racial-profiling/6936750
** assuming that English is the 'default language' for your project
@Random832: So the idea that statistical differences in ability between groups exist (regardless of the cause) is okay when it excuses differential outcomes, but not when it provides a reason to be accommodating of those differences?
Statistical differences in ability between groups can't be "okay" or "not okay". It's a fact of life that everyone has to live with. Would you say that gravity is "okay" or "not okay"?
Differential outcomes are also a fact of life that everyone has to live with. Nobody has a right to be part of a particular project. But everybody has a right to fork one or start their own. And everybody has a right to leave a project if they simply can't work with the other people on it. But nobody has a right to force those other people to "accommodate" if they choose not to.
What I can't understand is why people who claim to care about technical merit would even bother pestering project owners who clearly don't want to "accommodate" them. Why the bleep can't they just either fork the project or start their own? If they really think something technically better could be done in that project's particular area if only their wonderful contributions were accepted, the proper response is not to complain, it's to compete. Make a better project, and drive the one you don't like out of business.
(Actually, of course, I can understand why SJW's don't do this: it's way too much like actual productive work, and actual productive work is the one thing SJW's are absolutely allergic to.)
Why can't it just be "Women can't handle jackassery [ywnm] and that is one of several reasons why maybe it'd better to have less of it"?
Because this position is indistinguishable from "women are weak and need to be protected." The smarter of the SJWs realize this, so they try to reframe it as "jackassery is a tool of the patriarchary meant to keep us down so we have to root it out and eradicate it as if it were smallpox."
The right answer, of course, is to call out jackassery if it bothers you, and leave the group if it bothers you too much. The free market is very much at work in the open source world; it is not that hard to find laid-back small groups to contribute to.
@Bryan Lovely:
"it's really 'society' which should be fixed, but that's too hard, so we'll have to fix it one group at a time whether they like it or not."
That's a far too generous reading of what is going on. Nobody is agitating that healthcare discriminates against women, so it's not society. Nobody is agitating that deep sea fishing and trucking industries need to be reformed to add more women, or that there is systemic bias against men in the teaching profession.
No, these are skills that are perceived to lead to good jobs — well-paid, not dangerous — in a field that is dominated by men. So of course, that is perceived to be prima facie evidence of discrimination. The fact that the skills that are conducive to success in this field are often found in individuals who don't possess much tact makes for the occasional big, juicy target, who can be used to add fuel to the fire.
If they were just "fixing" one open source project at a time by carefully providing constructive feedback, that would be one thing. But they feel a need to make the entire open source ecosystem safe for women in one fell swoop.
Frankly, if you accept their premise — that the lack of female participation is due solely to rampant systemic misogyny, and further accept the (unstated in the case of the CoC, but stated often enough elsewhere) premise that these dictated changes would have a net positive effect on the ecosystem, then remaking the entire ecosystem may be the right answer, because "you're missing out on the potential participation of half the workforce" can be a persuasive argument.
But even if it's true — even if a lot of women who would usefully participate are put off solely by the atmosphere, tactics designed to highlight misogyny (or, even, if some reports are to be believed, create misogyny out of whole cloth) are the wrong answer — attempting to prove that the system is fucked up in this fashion (e.g. calling out Linus Torvalds and then quitting) is not likely to bring in the mellow recruits that could make it all better.
@Patrick Maupin: "you're missing out on the potential participation of half the workforce" can be a persuasive argument
A persuasive argument for forking or starting your own project, yes. :-) But a persuasive argument for coercing everyone else to conform to your standards? Absolutely not.
(I know you know this, I'm just addressing in advance the inevitable SJW response.)
@Patrick Maupin: I'm not accepting the premise; I was paraphrasing Random832 on 2015-11-17 at 01:33:29:
And attempting to point out that stating the problem that way implies coercion as necessary to the solution.
@Bryan Lovely and @Peter Donis:
Yes, I think we're in violent agreement.
FWIW, here's an interesting data point:
https://www.newscientist.com/article/dn22107-stress-may-cause-womens-brains-to-age-prematurely#.UeahCU396Uk
As we all know, STEM (as practiced in the US, anyway) can be quite mentally stressful, even before you add in the interpersonal crap. I wonder if some women instinctively shy away from it for purely biological reasons (even though their biology also makes them more than smart enough to participate at a high level).
> And attempting to point out that stating the problem that way implies coercion as necessary to the solution.
It really doesn't. There's no reason not to try to convince people to change their behavior, and there's no reason to stop trying to convince them, and none of that is coercive.
The no-jackassery standard is a red herring anyway. It's intended to make the SJW position sound good and anyone arguing against it sound like a jackass. And to draw out (for the purpose of discrediting) those who would defend jackassery while admitting that's what it is.
But if you attempt to apply the SJW standards to SJWs, they squirm out of it so fast you'd swear they were greased. They'll attack someone for their harsh tone, but if they are ever harsh they'll swear it's wrong to tone-police.
As Peter Donis notes, it's just chimp power games.
No-one's really advanced any argument for not stopping the… I really don't think "jackassery" is the right word, but I'm not sure what is… No-one seems to have any argument for it beyond "we want to and you can't make us stop" and maybe "spending absolutely any thought at all on anything non-technical like getting along well with others is a 'distraction' and therefore bad for the kernel"
You can make observations on what someone's desire not to do something says about them without forcing them to do that thing.
> It's intended to make the SJW position sound good and anyone arguing against it sound like a jackass.
Or maybe this is a symptom of the fact that there's no "the SJW position", just some people with good positions and some people with bad positions, all being grouped together (largely by their opponents) under the single banner of "SJW". Maybe if you didn't reflexively oppose absolutely any position that pattern-matches as "SJW", you wouldn't sound like a jackass.
It's not software, but my code of conduct on the Abandoned Rails facebook group is very simple:
1) it's got to be abandoned.
2) it's got to be railroad.
3) those are obvious and should go without saying. Part from that, there is only one posted rule:
Rule #1 for this group is: if you don't like something, report it. Don't whine. Don't comment on how awful a posting it is. Don't post a picture of a can of spam. Don't say "Moderator". Don't comment on it at all.
Instead, report it: There is a grey angle in the upper right of every posting here. If you click on it, one of the menu entries will be "Report to Admin". Click on it. People who report posts help make the group better. People who whine make the group worse. It's kinda like parenting, only with 11,551 children, nearly all well-behaved, a few not so.
> > "Tell that to Antifa, the state sponsored thugs that go around beating up dissidents."
> I would like to know how the "state-sponsored" part is determined?
Fairly often Antifa attacks groups that could crush them like bugs if allowed. Police protect Antifa from the groups that they are attacking, but do not protect the attacked groups from Antifa. They don't keep the peace against Antifa, but do keep the peace in favor of Antifa.
Thus, for example, when Antifa clashes with UK-IP on private property, UK-IP effortlessly throws them out like the limp wristed gays they in fact are, but when they clash with UK-IP on the streets, Antifa effortlessly owns the streets.
No-one's really advanced any argument for not stopping the… I really don't think "jackassery" is the right word, but I'm not sure what is
Well I have several times. Perhaps I was insufficiently clear:
Political dissent is defined as evil. Horribly evil. And the standard for what constitutes dissent shifts ever leftward, justifying any destructive measures you can apply against anyone, such as framing Linus and Julian Assange for rape.
You are not proposing to silence jackassery. You are proposing to silence dissent, where the standard for what constitutes dissent moves rapidly leftwards.
Notoriously, social justice warriors regard any dissent as bad behavior and any dissident as an evil person. If you have a code of conduct that forbids contributions by people that supposedly behave badly, you forbid contributions by dissidents.
@Random832: There's no reason not to try to convince people to change their behavior, and there's no reason to stop trying to convince them, and none of that is coercive.
You are using the term "trying to convince" to refer to taking away people's jobs, getting them charged with harassment, and shoving a Code of Conduct down their throats. That is an…interesting…use of language.
Also, even if we restrict attention to activities that are appropriately described as "trying to convince", there is a reason to stop trying: because the person you're trying to convince tells you to shut up and leave them alone. Persisting after that is no longer "trying to convince".
No-one's really advanced any argument for not stopping
No one has advanced any argument for why it should stop, either. "It's racist/sexist/insensitive/discriminatory/etc." isn't a argument, it's an opinion. Or a tactic.
You can "make observations" that cause them to lose their jobs, get charged with harassment, and have a Code of Conduct shoved down their throats, yes. But hey, you're not "forcing" them to do anything; you're just "making observations". And we have always been at war with Eastasia.
>You are using the term "trying to convince" to refer to taking away people's jobs, getting them charged with harassment, and shoving a Code of Conduct down their throats. That is an…interesting…use of language.
No, I am not. I haven't done any of those things, nor proposed doing any of them. To my knowledge, neither have any of the people who have complained about LKML culture. Even if some people have, that doesn't make other people, unconnected with them, guilty by association.
>You are not proposing to silence jackassery. You are proposing to silence dissent, where the standard for what constitutes dissent moves rapidly leftwards.
Saying "We don't fucking break userspace" instead of e.g. "It is not acceptable to break userspace" has nothing to do with dissent.
@Random832: I haven't done any of those things, nor proposed doing any of them.
Then at what point do you draw the line? Where does "trying to convince" stop and something not justifiable begin? From what you've said, the only answer I can see you giving is "nowhere".
But it might have a lot to do with getting an important point across. Remember, the person who submitted the patch that broke userspace had already heard/read Linus say "It is not acceptable to break userspace" umpteen times. Yet he did it. So clearly "It is not acceptable to break userspace" wasn't enough.
How about people decide themselves what they want to say, and how they want to say it, rather than you and your fellow busybodies?
But the former does more clearly show the resolve of Linus. Also, it is more predictive about what is needed to change his mind. Therefore, the former formulation will make kernel work more efficient than the latter.
I do not know everyday use of spoken English in the US, but I understand from others that the former formulation is in common use by men and women (and children). So Linus' use of English in message lists conforms to the global trend to use spoken language formulations in online conversations.
In short, I think Linus use of words is fully justified: It is clear and unambiguous, efficient, and aligned with common use.
Btw, the people who complain about Linus' rants are never those addressed by Linus. It is always non-involved people, bystanders, who take his words out of the wider context if the conversation and feel enraged.
"Police protect Antifa from the groups that they are attacking, but do not protect the attacked groups from Antifa. They don't keep the peace against Antifa, but do keep the peace in favor of Antifa."
As usual, what's sauce for the goose is not sauce for the gander for you.
On the streets, the police has the task to quell violence, any violence. So they protect both sides in the dispute. They are not perfect in it, and it depends on how well they are able to predict the problems in advance. Obviously, it must all be the fault of the violence of the "other side".
Anyway, that is very, very far from "state sponsored Antifa".
>Saying "We don't fucking break userspace" instead of e.g. "It is not acceptable to break userspace" has nothing to do with dissent.
Well, one hand, this is just like saying the General Patton School of Diplomacy is not always the ideal social lubricant, and that is everybody who works in an office, goes to church or has a dinner with his aunt has to accept at some level, so this could be OK.
Still, it is slightly, I repeat, SLIGHTLY anti-male, because IRL men cuss even in a business professional environment when the ladies aren't around, the GPSD (see above) is a sort of a male social lubricant and trust builder, and one of the best way women can get accepted as one of the boys is by cussing, smart ones usually figure that out fast. And in that sense political, although OK, it is not a big deal. Just watch really hard it towards not slipping more and more toward policing typical male behavior. And be aware that you are breaking a certain level of camaraderie by this rule – things get a bit too official. You are removing the project from the locker room and putting it into something like an office. Are you sure you want to do that? It has consequences.
I've written up a proposal for a software contribution policy that is intended to reject the SJWs' attempts to force crap code down our throats in the name of equality. Comments are welcomed.
People who have an allergic reaction to schoolmarms are also an identity group and perhaps an unusually productive one.
At this point i might have lost track of what you're trying to stop but (assuming i'm still on the right track) i think you're looking for this quote from Linus on LKML :-
The fact is, people need to know what my position on things are. And I can't just say "please don't do that", because people won't listen. I say "On the internet, nobody can hear you being subtle," and I mean it.
And I definitely am not willing to string people along, either. I've had that happen too—not telling people clearly enough that I don't like their approach, they go on to re-architect something, and get really upset when I am then not willing to take their work.
I've seen Linus say this in other ways but this was the easiest to find direct quote. You can say it's a terrible argument if you like (Sarah Sharp did) but it definitely exists.
michael on 2015-11-18 at 09:24:46 said:
Since you seem to be planning to do a code of conduct, a few suggestions that I hope you will use. To be honest, I still think most projects are probably better without one but since there seems to be a risk of it becoming really widespread or at least widely copied it had better be done right. If you can make it good it will force others who want to do a different one to have to be better. Please see if you can get some support from one of the friendly / freedom oriented lawyers with a history of making stuff simple too.
* so far most codes of conduct don't seem to address real issues that have caused serious problems in F/OSS projects. If there has to be a code of conduct it would be good if it was useful.
* Having a code of conduct which addresses a few issues but doesn't address an important issue _might_ be worse than not having one at all. "I didn't think your project cared about patents; it's not mentioned at all in the code of conduct; anyway too late now, your users all owe me the license fee". At the very least the CoC should state clearly that it is limited to some cases.
* there are lots of different opinions; any code of conduct should probably have some options. E.g. some people care about code assignments, other people don't want them. GPL people want compatible copyleft in their forums, OpenBSD people want less licensing etc.
Freedom of speech is a fundamental issue for most FOSS branches; something should be said about this.
* "we don't care about…. lifestyle, political viewpoint, or anything" – is good (from Maynard)
* however "our forums are for discussion of our software, please keep extraneous discussion outside the 'offtopic' forum" is better
* "other people's political views outside the project should not be brought up inside the project unless directly relevant to their project activity" might be good too.
There should be some statement on commercial interests:
* "all contributors are expected to declare if they make a suggestion or contribution on behalf of someone else who is paying them in money or in kind"
* "This project has lots of secret contributors and does not expect declarations of commercial interest. That privacy is important in keeping ongoing cooperation in the project. Please do not attempt to force contributors to declare their interests."
There should be some statements about patents
* "contributors who are aware of any patent risks should declare them to the project board"
* "this project is based in a software patent free country, contributors and users from software patent inhibited countries are responsible for their own legal situation"
there might be some statement about forking
* "We discourage project forking, we would rather see a branch within our own repository. Maintainers involved in an unjustified fork may lose their status. Valid contributions and backports will be accepted however"
* "project forking is a major part of FOSS development. We encourage it, however project maintainers involved in a long term fork are required to make it available in a public Git repository or risk losing maintainer status"
there should be a clear statement against oversensitivity
* "Our project accepts contributions from many people from many different cultures and we want to be welcoming to those who's first language is not English or who do not have traditional education. Contributors should avoid over-interpreting statements and finding insult where none was intended. If you find a comment disturbing or insulting then please try to resolve it with the poster a manner which does not disturb the functioning of the forum. In a case where direct resolution fails please contact the moderator for support."
it would be really good to say something about maintenance
* "Contributors of large sections of code are expected to maintain and support their contributions, at least for a period (one release?) after acceptance, providing fixes and explanation. Contributions from contributors with a clear record of support will normally be preferred over equivalent contributions from those without such a history. "
security is important in many projects
* "contributors are expected to declare any security issues they are aware of in their code".
* "contributors are expected to follow the security guidelines listed in XXX"
* "contributors should declare the security measures they have taken"
@Jay Maynard
Surprisingly, brief though it is your statement says too much. "We will accept contributions…" should probably be "We will give serious consideration to contributions…"
* Sometimes it has happened that projects don't accept perfectly good code simply because it doesn't fit their chosen direction. E.g. (if memory serves) real time patches to Linux have been rejected from mainline because they risked making maintaining normal non RT Linux more difficult.
* Sometimes it has happened that a large code contribution is not accepted because the maintainer has a history of not following up. E.g. reiserfs updates (seems prescient from today's point of view).
* It's also quite reasonable not to want to accept a contribution for reasons of stylistic disagreement (e.g. adding full power closures to Python would not match python style even if it might be considered "good")
There's no right to have code included. At most there is a right to have a explanation of why it wasn't accepted combined with the right to fork.
Re: patents –
The open invention network has created a demilitarized zone around linux, with a HUGE patent pool that I hope defangs all the trolls, as well as neutralizes a ton of overbroad patents in general.
I just joined, after learning that google and Cisco were licenses, including quite a few other firms. I sleep better, now. I used to hate waking up with a "new" idea.
http://www.openinventionnetwork.com/community-of-licensees/
Re: Code of Conduct
Don't assume that once a CoC is developed and implemented that the problems will magically go away or the antagonists will suddenly disappear. Sometimes this sort of defensive response prompts them to redouble their efforts or modify their tactics. And don't make the mistake of assuming that this issue is solely an instance of good faith disagreement about sensibilities in the workplace. In other words, don't drop your guard or ignore your six.
Michael, you make good points. I added a section to the policy draft:
If we reject your contribution, it means only that we do not consider it suitable for our project in the form it was submitted. It is not personal. If you ask civilly, we will be happy to discuss it with you and help you understand why it was rejected, and if possible improve it so we can accept it. If we are not able to reach an agreement, then you are free to fork our project, as with any Open Source project, and add it to your fork.
There's no reason not to try to convince people to change their behavior, and there's no reason to stop trying to convince them, and none of that is coercive.
in the second post by djangoconcardiff, they wrote "I urge you to reconsider for the good and future of this project :)" [sic] and their final post made what this meant clear: "I will be forwarding the content of this issue to the Chair to evaluate your continued presence in the DSF." Now, you claim this is not coercive, but in order for me to agree with you I must know one thing: does djangoconcardiff speak on behalf of [legitimate] authority?
If a manager in a store, the bouncer in a bar, or a park ranger tells me I need to leave, they have the authority and right to eject me for (nearly) any reason whatsoever. However, if a random person tells me I need to leave a communal space —unless I'm clearly obstructing their usage [such as walking through a wedding photo] they most likely don't have sufficient grounds or authority to eject me, and any attempts to do so on their part will be bulling and coercion.
That's the most puzzling element of this whole tale to me. Djangoconcardiff has no commit history, so the fact they responded to a refusal not by justifying the request but with "I will see you get kicked out of the community for this"—well, that seems like someone acting as a bully and trying to coerce the behavior they want, without proper authority.
I'd be interested to know what causes you to see things differently, because to me this looks like almost like a textbook example of coercion.
@Alex K, I will not dignify with a response your attempt to unilaterally reframe my argument as applying to djangoconcardiff's actions.
> I will not dignify with a response your attempt to unilaterally reframe my argument as applying to djangoconcardiff's actions.
You haven't provided any reason to think that your proposed program is not, consciously or unconsciously, a stalking horse for djangoconcardiff and the like.
Or do you think that they'll just magically disappear once Linus is convinced to stop using the word 'fuck'?
I've already made clear what I think of reflexively grouping together any position that pattern-matches as "SJW" and assuming any individual who holds one of them holds all of them.
Okay, so here's the connection.
The SJWs (here defined excluding you) make it their explicit goal to kick anyone who violates their idea of PC out of any group they can manage, including groups which have nothing to do with the debate, even when that damages the nominal purpose of the group. They have, empirically, begun attempting to implement this agenda by forcing codes of conduct on open source projects, using the acerbic tone of discussion in some projects as an excuse.
You show up here talking a whole bunch about how the acerbic tone of discussion is really a problem, and the people who are reacting against the SJWs have no good reason to oppose them, because they're just trying to improve the tone.
Even assuming you are sane and reasonable — an assumption I'm entirely willing to grant — you are giving cover to their agenda, while nowhere (that I can see) condemning their actual enormities. It is hardly surprising that people therefore make assumptions about your other positions, or attack you along with the SJWs. Orwell's discussion of "objectively pro-fascist" comes to mind.
I like your contribution policy. However, code isn't the only kind of contribution, particularly on large projects; there is: documentation/man-page/FAQs, bug reports, art-work/web-content…. um… with authorization from the project leader: dealing with email, moderating forums
I like your proposed contribution policy, but I have one suggestion; in the last bullet, the "from anyone" one, I would take out the second sentence. It's not necessary, and IMO as soon as you start listing specific categories, even if you add a disclaimer that the list is not all-inclusive, somebody will complain that you didn't list their pet category.
Also, listing the categories at all invites the inference that group identification on the basis of these categories is legitimate in the first place. But that is precisely the mindset we are trying to combat.
> They have, empirically, begun attempting to implement this agenda by forcing codes of conduct on open source projects, using the acerbic tone of discussion in some projects as an excuse.
I think you're confusing at least two different incidents.
"At which point I'm likely to say something like "You've found me out. I am, in fact a mere simulation of ESR running on a darknet supercomputer buried beneath the Transylvanian Alps,""
But can the real ESR pass the Turing Test?
Brian: You're right about that. I tried to address it, but it needs more generalizing. Will fix.
Peter: The listing of categories is quite intentional, as examples of the kind of arrant pedantrysilliness up with which we will not put. The bit about "or anything extraneous like that" is intended to be an answer to the "you didn't include my grievance-group-of-the-week!" BS.
@Jay: Fair enough.
If your arguments regarding LKML culture cannot be applied elsewhere, it is far more enlightening to receive an explanation why than the simple statement "that's so wrong I won't dignify it with a response". Why, one might argue the piquant tone of the latter implies the speaker can't rebut the argument as presented.
@AlexK – considering neither the (real or imagined) problem, nor the people involved on either side, nor the tactics, are even remotely the same, I don't see what either one has to do with the other.
>> "Police protect Antifa from the groups that they are attacking, but do not protect the attacked groups from Antifa. They don't keep the peace against Antifa, but do keep the peace in favor of Antifa."
> On the streets, the police has the task to quell violence, any violence. So they protect both sides in the dispute.
If they protect both sides, how come Antifa is able to clear its vastly more numerous and powerful opponents off the streets. If they protect both sides, should not the other side, the side that antifa opposes, be able to hold a peaceful protest?
UK-IP hires a hall and invites the public. Antifa infiltrates the hall, and when the show starts, start disrupting. Without the inconvenience of police presence, UK-IP casually sweeps the disruptors out of the hall with force so firm and overwhelming that there is almost no fuss.
Try the same thing in the street, when police apply their thumb on the side of antifa, and it is UK-IP that gets swept off the street.
> If they protect both sides, how come Antifa is able to clear its vastly more numerous and powerful opponents off the streets. If they protect both sides, should not the other side, the side that antifa opposes, be able to hold a peaceful protest?
Maybe because the goal of a society in which peaceful protests are a valid form of speech is much better served by having demonstrations in an orderly manner (i.e. one group gets the street at a time) rather than having crowds of people push each other around by weight of numbers?
And maybe the fact that private UK-IP venues are able to eject them comes from, you know, the fact that it is private property and Antifa has no right to speak there, rather than because this is somehow happening under the police's nose. Otherwise why wouldn't they just call the police to the location in advance of starting the disruption, if police presence guaranteed an Antifa victory?
You might as well claim the KKK and the Westboro Baptist Church are state-sponsored.
> I've already made clear what I think of reflexively grouping together any position that pattern-matches as "SJW" and assuming any individual who holds one of them holds all of them.
Social Justice Warriors are conspiratorial and entryist. Thus it is reasonable to assume secret ulterior motives in anything done or said by someone who pattern matches to a SJW.