[lmilcin]

The problem with Clojure is that it is too good. It gives you, the programmer, too much freedom.

Most people do not have problems that require so much freedom.

Most people do not know what to do with that freedom -- they don't have enough experience actually organising their applications.

Most people benefit from using a language/framework that requires them or at least rewards them to put things in a certain way. For example Java Spring rewards people for following a certain application design -- you can break rules but then you are on your own and Stack[Exchange|Overflow] examples can no longer be copied/pasted directly into your codebase.

As much as I love Clojure, every single corporate Clojure project I have seen in the past was an utterly unmaintainable mess.

I have never actually participated in a Clojure project (I use Clojure mostly for rapid prototyping/PoC-ing), but what I figured is that Clojure requires minimum maturity from the developer and especially drive to be constantly simplifying things -- which is unfortunately very high bar. Most developers I work with / interviewed do not really understand what it means to refactor and simplify. Most people are only focused on the part of the work when they get something to produce expected values and everything else just isn't high priority in a corporate environment.