Slashdot Mirror
Could Go Community's Threat of Public Shaming, Lifetime Bans Make Go a No-Go?
theodp writes: At first glance, the proposal for A Code of Conduct for the Go Community (attributed to Google's Andrew Gerrand) seems reasonable enough. How can you argue with the goal of treating everyone with respect and kindness? But the Devil is in the detail, and the proposed Code notes there soon could be consequences for calling someone an "idiot" or saying something is "so simple even my grandma could understand it" (the latter "marginalises women and the elderly by implying that something need be simple for an old woman to understand it"). And the punishment meted out by the Go Code of Conduct Working Group to those who find themselves on the receiving end of an anonymous complaint could be anything from nothing to "a request for a private or public apology, a private reprimand from the working group to the individual(s) involved, a public reprimand, an imposed vacation (for instance, asking someone to 'take a week off' from a mailing list or IRC), or a permanent or temporary ban from some or all Go spaces (mailing lists, IRC, etc.)." And no, this doesn't appear to be a goof. So, might individuals and companies think twice about embracing a programming language whose community's Code of Conduct threatens to ruin reputations and ban people from technical support resources for life? Too late to get this added to the list of questions for Alan Donovan and Brian Kernighan?
Shaming a shamer is still shaming, you shame shaming shamers!
Shame on you!
Even Andrew's Grandma would think his code of conduct silly, he should talk to her about it
On a positive note, the code they likely to produce will have very robust privilege checks.
First they came for the BASIC programmers, and I did not speak out—
Because I was not a BASIC programmer.
Then they came for the go programmers, and I did not speak out—
Because I was not a go programmer.
Then they came for the canines, and I did not speak out—
Because I was not a canine.
Then they came for me—and I told them to GTFO my mailing list.
I've fallen off your lawn, and I can't get up.
Mellow greetings, special butterflies.
Today (not to disrespect those on the other side of the national dateline - when I say today, I mean everyone's today!) I (with full credit to everyone everywhere, of course) would like (this is not a statement of exclusion for things I don't like) to introduce SJW, the language you can share without fear (not that fear is wrong, of course.)
SJW:
o No insert() function: Instead, we have crafted a flawless nomeansno() function
o Fully complementary yesmeansno() and maybemeansno() functions
o No try:, because every function generates an exception!
o exit() has been replaced with aloha().
o Procedure calls have been replaced with the respectful request paradigm, which obey the global mood settings
o 100% private internal assumption for all functions; offering data requires guessing if the function will take it or crash (exceptions guaranteed)
o Every access from within a function to another function must be embedded in a call to politewrapper()
o politewrapper() implements infinite recursion by use of counters instead of ever returning up a level
o Every function ends with a sequence of calls to apologize(), cleanup() and washreturnvalue()
o All programs will be created equal: all code is treated exactly the same and does exactly the same thing, which is apologize for running.
I've fallen off your lawn, and I can't get up.
I'm offended by the mailing list name golang-nuts because "nuts" is a slang term used to refer to testicles. By naming the mailing list golang-nuts it indicates that it's a male dominated mailing list where women (those without "nuts") are not welcome. Please change the mailing list name to be more inclusive.