It is a valid point I don't know why the downvotes. I think Rich had to make a decision, writing a completely new LISP from scratch or leverage an ecosystem an

It is a valid point I don't know why the downvotes. I think Rich had to make a decision, writing a completely new LISP from scratch or leverage an ecosystem and create a LISP on the top. >> In Clojure, is almost the same, most Java libs are over-engineered and horrible to use but you need to reach for them because Clojure lacks an ecosystem. The biggest problem with Java libs the mixed quality. Many big data project have this problem, if you peek under the hood you gonna be amazed about abstractions leaking into different bits and pieces of the system. My favourite example how ORC imports Hadoop FS https://github.com/apache/orc/blob/master/java/core/src/java/org/apache/orc/OrcFile.java#L31 https://github.com/apache/orc/blob/master/java/core/src/java... There is one more problem with Clojure that I find annoying, the actual Java interop. I was running into issues with this many times and some Jave libs are almost unusable without a thin wrapper written in pure Java. Other than that, I think Clojure is still one of the best options out there.