David, While it is a very detailed and good document, my reaction is that it isn't an appropriate one for business to make the switch. I suspect they will not see any "value." I'm not sure what background your boss has, but if the boss isn't into code and only cares about managing the team and the product and the timelines, this document will not help sell.
I'm in a similar boat, but luckily in a position to drive some change. I'm the only technical guy (out of 2), but the product was developed for a long time before I joined (outsourced). It's PHP, and cost and finding people to do it were the main reasons my partner went that route. I'm a big fan of Clojure, with little to no Javascript experience. And we are building (of course) a web application. PHP will not go away any time soon from our app. So, I'm trying to find the best way to move away from PHP, and into Clojure-land, but via familiar territory. Right now, I am building some new features for our Chrome extension, and need Javascript. Every time I tried doing JS, I would compare (mentally) with how easy it would be in Clojure. I finally just threw away a big part of it (a pre-existing version) and started coding it in Clojurescript. It's just the beginning, but I've seen substantial progress in a single day, given my JS experience - lack of it. So, this is the way I am going. [I wrote the above a week ago, and it was in draft] And just now, we released a chrome extension, with a big chunk written with clojurescript (and reagent, sablono, storage-atom, and really great help from weasel). Extremely happy about it, and excited because of the new-found confidence in being able to do UI. I feel the safest way to go (with nay-sayers, or hurdles along the way) is the one-small-step-at-a-time. But I'm just repeating common knowledge, which is always profound with the benefit of hindsight. :) My 0.02 is a currency unit of your choice. Ravindra On Wed, Mar 12, 2014 at 5:00 PM, <da...@dsargeant.com> wrote: > I just spent the day writing this document for my boss, called "The case > for Clojure." I hope it helps. We are in exactly the same boat, so it > should be extremely relevant. > > P.S. If the company I work doesn't make the switch I plan on looking for a > new position. So hit me up if you're in need of another Clojure developer. > > David > > -- > 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.
