On discussing the 2% of respondents who found the Clojure community to be a problem:
...rather than simply bask in the awesomeness of the Clojure community, let’s ask: is it possible to make that number be 0% next year? What can we do to minimize those negative interactions? Are they caused by random misunderstandings, or are there just a few bad apples?
This is how programming communities should be discussed. This statement gives me hope.
#clojure on freenode is glorious. I've never seen such a round-the-clock cadre of participants in an IRC channel who will take the time to give such thoughtful explanations. It reminds me of a time before the explosion of documentation for about everything on the web, when going to an IRC channel was the authoritative way of getting hard questions answered.
I find #python similarly useful, although people do tend to be less patient and more likely to tell you you're wrong (which I think is good, most of the time).
I haven't touched Clojure yet, although discussions on HN have made me interested, and getting a solid grasp on functional languages seems like the next logical step in my evolution as developer.
If you had to point a newcomer to a single 15-30 minute resource - blog post, tutorial, code sample, whatever - that can give them a true "aha!" moment about Clojure, what would it be?
Rich's talk at the JVM language summit, "Are We There Yet?", gives a really good look into some of the ideas that underlie clojure. It's worth viewing even if one never uses clojure.
Frankly, I don't think such a thing exists that matches your constraints. Maybe if you're experienced with FP and with the JVM, I suppose? but the 15- to 30-minute aha! moment?
Clojure is, in its own terms, an identity not a value(see http://clojure.org/state). At the risk of torturing a joke beyond breaking point maybe it should be "State of @Clojure".
As was noted in the article, protocols and multimethods seem to be somewhat undervalued by the community. Maybe its because so many new users come from Java, Ruby and Python, where you only have standard OO(whatever that means). It would seem prudent to me to address this issue, and popularize them more, with more tutorials or blog posts.
I don't use clojure much these days, but in Common Lisp I use generic functions(the original inspiration for protocols and multimethods) all the time, and find them the second most important feature of CL after macros.
...rather than simply bask in the awesomeness of the Clojure community, let’s ask: is it possible to make that number be 0% next year? What can we do to minimize those negative interactions? Are they caused by random misunderstandings, or are there just a few bad apples?
This is how programming communities should be discussed. This statement gives me hope.