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.

Luckily, you don’t *have* to convince your boss to use Clojure. You only have 
to convince your boss to use the JVM. Whether that means Java, Scala, Groovy…or 
whatever. These languages and their respective libraries have come a long way, 
so it wouldn’t be the worst thing in the world to have to, for example, start 
with Java and Spring. But! Once you’ve got a JVM up and running then it’s 
trivial to sneak Clojure in the back door, as it were.

It’s much easier to convince someone with code than arguments, and if you’re 
already getting push-back from management on Clojure, then even if you do 
convince them to use Clojure, I bet you will not have so much fun. Trust 
me…I’ve been there. If you do, be prepared for every bug, every delay, every 
tiny hiccup to be blamed on Clojure.


On Wednesday, August 20, 2014 at 13:37, aboy021 wrote:

> Is Clojure a suitable language for a company that needs to grow quickly?
>  
> If a company wants to be able to hire staff and get them up to speed, as well 
> as have options for bringing in contractors and outsourcing some work, is 
> Clojure a good choice?
>  
> We've had trouble finding Clojure devs, and others have complained of how 
> hard it is to learn Clojure and read the code from open source projects, 
> especially for those with backgrounds in languages like C++.
>  
> I think Clojure should be a good fit for us because it is expressive, 
> flexible, and we are still discovering new aspects of the problem domain. I'm 
> biased on this because I really enjoy Clojure at home, and want to use it 
> commercially.
>  
> I'm really looking for arguments that will help me persuade my boss that the 
> risk of starting our next project in Clojure is one worth taking.
>  
> Thanks for any suggestions.  
>  
> --  
> 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 
> (mailto: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 
> (mailto: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 
> (mailto: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.

Reply via email to