Results of the 2011 State of Clojure survey

On discussing the 2% of respondents who found the Clojure community to be a problem:<p><i>...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?</i><p>This is how programming communities should be discussed. This statement gives me hope.

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.<p>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?

Why is the "State of Clojure" held more than once ever, let alone annually? Everyone knows Clojure's state never changes.

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.<p>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.