This is the fourth year in which I’ve offered up a “State of Clojure” survey. As before, my intention is to get a sense for the size and overall level of activity in the Clojure community, and to capture a certain zeitgeist of the community’s mood, practices, concerns, and so on. If you’re interested in history, you can see the results of all prior surveys:
The big change this year is that questions related to ClojureScript are included such that it roughly shares the limelight with Clojure. In part, that’s selfish; I started using and contributing to ClojureScript seriously over the last 18 months, so I’m interested to have some perspective on what other users care about. More importantly, there’s no denying that ClojureScript has matured significantly over that period, and has attracted a great deal more attention. Especially given its potential, it’s time it took its proper place in the survey as a peer implementation of the Clojure Principles we’ve all come to appreciate.
Results from the 2013 State of Clojure & ClojureScript survey are here.
This year, I’ve moved to hosting the survey with PollDaddy, which has graciously set me up with a ‘pro’ account; this will allow us to get far more advanced analysis out of the results than were ever possible with the primitive Google Docs form I’d used up until now.
As before, I’ll follow up with the results, some charts and graphs, and some sad attempts at witty commentary. Of course, all of the raw data will be available as well.
Finally, please do what you can to spread around this survey to those that you know of that are working with Clojure and/or ClojureScript.