On Mon, Jan 7, 2013 at 3:02 PM, David Jacobs <da...@wit.io> wrote: > 1. Would it be harder to hire if we built our apps with Clojure? More > specifically: Hiring for people who know about or already love Clojure/FP is > certainly a nice filter for talent, but is it too stringent of a filter? > What percentage of the Clojure community wants to code Clojure > professionally but isn't right now? Do we have metrics on that?
Harder to hire for Clojure development than what? The pool is certainly smaller than Java, Groovy, C# and even Scala. One upside I've found is that a lot of developers seem to be excited about the possibility of coding in Clojure and, whilst the pool of active Clojure devs is pretty small, the attractiveness of your job / company goes up by offering (non-Clojure) devs the option to learn / write Clojure on a daily basis. As long as you're prepared to shoulder the burden of training those developers. As for metrics, I can only say based on a survey conducted of the Bay Area Clojure meetup members: out of 700+ members, we had 52 responses. Of those 52, 40% were using Clojure for main line production work, 17% were using Clojure for utilities / ad hoc projects at work, and 10% were evaluating Clojure at work. In other words, a third of responses were not even at the evaluation stage. However, based on informal show of hands tallies at our meetups, only about a third of attendees say they are using Clojure at work. We get 30-50 attendees at our meetups. So, it's a small sample either way, and not entirely consistent. I'd be more inclined to think that of the "Clojure community" at large, at most a third are really using Clojure at work. Chas Emerick's "State of the Union" survey meshes with that, with 38% of respondents in his 2012 survey, saying they use Clojure at work: http://cemerick.com/2012/08/06/results-of-the-2012-state-of-clojure-survey/ Biased of course by people being more likely to respond if they are actively using Clojure for _something_... > What other tips do you have for convincing an employer that Clojure makes > good business sense? (Of course I've already told them about domain-tailored > abstractions, containing complexity, the ease of data manipulation with a > functional language, etc.) I would add "easier concurrency" to that list. I think an argument could also be made for "easier maintenance" based solely on the much small codebase you are likely to have with Clojure compared to, say, Java. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
