Disclaimer: I personally prefer clojure, but earn most of my money as a consultant &#x2F; coach helping clients develop Java code.<p>For Java code, it&#x27;s often easier to predict the performance characteristics of a part of the code. But you shouldn&#x27;t trust your judgements anyway - instead use a profiler - so this is not really a reason.<p>Speaking of performance: I once talked to someone working for Elasticsearch, and they told me that they cannot use clojure for most of their code because of their performance requirements. Clojure collections are almost as fast as Java collections in many scenarios, but that is apparently not fast enough for them. This is probably not a valid reason for most projects, though.<p>There is a huge number of Java developers out there, and Java is easier to learn for someone coming from C++ or C# or JavaScript than clojure (at least I am pretty sure about that). So hiring cheap developers might be easier if you use Java. You might count that one as a political statement.<p>There are some great tools for Java out there: IntelliJ Idea, Yourkit Profiler, JRebel, ... Cursive Clojure is great, but IntelliJ for Java has even more integrated workflows.<p>There are very mature open source libraries &#x2F; frameworks &#x2F; tools for Java: JUnit, Spring, Guice, Dropwizard, Gradle, Elasticsearch, ... You can have commercial support for many of them. Most of the libraries I use with clojure are version 0.3 or something like that with no possibility for commercial support (but they work fine anyway).<p>Static typing: A lot of people complain about it, but it can really help you to create maintainable code. See for example <a href="http:&#x2F;&#x2F;talks.samirtalwar.com&#x2F;use-your-type-system.html" rel="nofollow">http:&#x2F;&#x2F;talks.samirtalwar.com&#x2F;use-your-type-system.html</a>