Didn't see this survey in time to contribute, but I'm one of the tinkerers who's used CLJS more than Clojure. Most of what I've been interested in doing is in-browser. For my last project[1] I used a regular Clojure REPL to clarify my understanding of the standard lib and paste in little functions for testing. Don't remember why I didn't use a browser-connected ClojureScript REPL. Maybe it just didn't seem worth typing "rlwrap lein trampoline cljsbuild repl-listen" when I can type "lein repl" :P<p>My biggest wish is for the ClojureScript compiler to be less accepting of stupid code. I've made all kinds of moronic mistakes[2] that would ideally yield a warning or even a straight-up error, right at the source, but they don't and I just end up finding data structures full of nils at runtime. I've also hit a few traps with lein-cljsbuild[3][4]. This is all definitely improving though.<p>I've now started my first real Clojure project, a web app built on Luminus[5]. Luminus kind of strikes me as training wheels for Clojure. It's easy to get started with, and minimizes the sense of foreign-ness coming from a Python web development background. But I doubt I'll still use it once I have more experience, as opposed to simply putting its component libraries (Compojure, Ring, lib-noir, etc.) into a project directly. Which is fine; it fills a valuable role in the ecosystem anyway.<p>1. <a href="https://github.com/graue/dumbbell" rel="nofollow">https://github.com/graue/dumbbell</a><p>2. Example: <a href="http://dev.clojure.org/jira/browse/CLJS-639" rel="nofollow">http://dev.clojure.org/jira/browse/CLJS-639</a><p>3. <a href="https://github.com/emezeske/lein-cljsbuild/issues/239" rel="nofollow">https://github.com/emezeske/lein-cljsbuild/issues/239</a><p>4. <a href="https://github.com/emezeske/lein-cljsbuild/issues/248" rel="nofollow">https://github.com/emezeske/lein-cljsbuild/issues/248</a><p>5. <a href="http://www.luminusweb.net/" rel="nofollow">http://www.luminusweb.net/</a>
I recently undertook a serious effort to learn Angular.js for a work-related project. After some time, I reached the point where I think I finally "got it", and I was feeling pretty good about Angular.<p>Then I did a bit of work with ClojureScript and core.async. <i>WOW!</i> The difference is night-and-day. Even with ECMAScript 6 generators, vanilla JS will have a hard time competing with the CLJS/core.async combo.<p>Of course, CLJS is very young (somewhere between pre-alpha and beta), and core.async even more so. For that reason, I don't think it's that unexpected that there aren't many people using CLJS exclusively...but I would not be surprised <i>at all</i> if this changes in the coming years.
I tried using Clojure to build my personal website. I love it, and can't wait to see where it goes next. However, the documentation problem is pretty real. Clojure libraries get updated and deprecated really quickly (because the language is so new) and tutorials on the web quickly get out of date. I had a lot of experiences where I would pick up a new library or framework because it was in a tutorial, only to find out that:<p>-It had been abandoned by its creator in favor of a newer framework.<p>-The functions used in the tutorial had been deprecated.<p>These are definitely just growing pains and not something intrinsically bad about Clojure. However, I hope that the next year or two bring more stability and more ease of learning.<p>One thing that I wish was better tutorialized is LightTable. I understand Chris Granger is a one man IDE developer and that LT is still in development. However, if we could get more tutorials from users like the one that was posted earlier today, that would be fantastic.<p>Eventually I ran into pedestal.io. Those guys have a great framework. It covers front and back end, and involves Functional Reactive Programming, something I'd never seen before. They have an excellent tutorial that they update in sync with the framework. It's a bit overkill for my personal (mostly static) website, but after taking the time to learn it I feel like I came away with a real new skill.<p>One last thing that struck me about the Clojure community is how many workhorses there are. Guys like cemerick, technomancy and Chris Granger (the guy behind LightTable) have been working fast to build TONS of stuff, and a lot of it works really well. In particular, Leiningen is awesome and I imagine (I've never not used it) that it makes the process of getting started that much easier.
I don't have much time to drill down right now, but a quick search of the responses for "Name <i>one</i> language feature you would like to see added to Clojure" reveals 8/563 respondents wrote "Clojure in clojure" verbatim (disclaimer: I was one of those 8). The good news here is that this effort (in the guise of tools.reader, tools.analyzer, and tools.emitter) is very active and looks like it will yield many positive results in the near future.<p>(If you're curious <i>why</i> Clojure in clojure is important, in the recent Cognicast episode with Ambrose Bonnaire-Sergeant he give's a perfect example of how these tools make it possible to add a type system to Clojure.)
> “Staffing concerns” is new as the #2 reported frustration, which I think is significant: I certainly know that companies using Clojure have a hard time filling openings lately.<p>I'm profoundly surprised by this, and would have expected the opposite -- frustrated Clojure programmers wishing for opportunities to use the language in their day job. Is there a market failure here and can we fix it?
I'm curious if the issue with "lacking documentation" is an issue with explaining function inputs and outputs (like types would give you in other languages), expected behavior, or just bad discoverability for the long list of core functions.<p>When I was starting, I ended up just learning to read the function source because of the lacking documentation. It's a skill that has paid off in the end, but i'm not sure it was the best way.
>How would you characterize your use of Clojure today?<p><i>More than half of respondents are using Clojure at work, which is a big jump compared to the last two years, when only a third of respondents were so lucky. This is nothing but good.</i><p>People using Clojure in their work environment is a great thing.
I'm glad the survey highlighted the issue with clojurescripts repl ease of use. I know for myself this is the number one issue I would like resolved. If I could interact with the browser in a painless way I would probably ditch Javascript as my primary browser language and push for it at my company.