To add a data point to this, while the technology is great, it is not necessarily right for all companies at all lifecycle stages.
My experience has been that C++ skills and interests don't necessarily translate directly to Clojure. The kinds of microdecisions one makes in modeling, algorithm design and so forth are quite different, and the costs one optimizes for in C++ land don't make sense in Clojure. What I have seen more often is motivated C++ers transition to Scala- getting up to speed on the JVM and the APIs, get a little bit of a REPL, while retaining types and compilation and a lot of the mental model- and then go from Scala to Clojure. But since Clojure is a different toolchain and level of abstraction, changing both at the same time even for the motivated can be a bridge too far. I would also not look at Clojure as a commodity tool, in the enterprise IT staffing model where one wants to just be able to throw bodies at problems, shift them around between teams, scale them up and down quickly with fluidity between staff and consultant roles. It's currently significantly more specialized and elite than that. On the flip side, because it is a different level of abstraction, the right team + Clojure can be incredibly productive in a wide variety of domains. If you have a budget and can afford to frame a Proof-of-Concept in your domain for a consulting team to demonstrate this, I would highly recommend getting in touch with Cognitect themselves. I don't think it is widely known that aside from being the creators of Clojure and Datomic, they have an extremely proficient consulting practice. Watching them work can be mind-blowing, from both technical and management perspectives. On Wed, Aug 20, 2014 at 11:06 AM, Nando Breiter <na...@aria-media.com> wrote: > Perhaps the question is more "Is your boss (or company) suitable for > Clojure?" > > On Wed, Aug 20, 2014 at 2:56 PM, Joshua Ballanco <jball...@gmail.com> > wrote: > >> My advice on convincing your boss to use Clojure for a new project: don’t. >> >> Projects succeed or fail for any number of different reasons, but I can >> guarantee you that if you *start* a new project with Clojure, and it does >> happen to fail, then the choice of Clojure will bear the brunt of the blame >> whether it deserves it or not. > > > -- > 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 > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
