Clojure has many pleasant properties, but it’s painfully immature to a seasoned Lisp developer. That said, if I really wanted to use the JVM for business reasons, Clojure would be high on the list. Even so my gut instinct is ABCL.

Edit: response to child: The most obvious thing is a lack of TCO. But there are plenty of other things like the limitations of a JVM based object system compared to the MOP. And then there’s the Lisp Machine heritage that shows through in forms like EVAl-WHEN. There’s the condition/restart system too. That’s just a few things off the top of my head. But in no way am I denigrating Clojure. It’s a good Lisp that meets important needs and I’d happily use it anytime it’s right tool.

Actually they do use Clojure, at least they have open positions for Clojure Software Engineers. Also, I know that Vsevolod, the author of the article, is not with Grammarly anymore.

Development in Clojure is afaik noticeably different (or at least was in my experience) if only because Java quickly surfaces for example in backtraces. You also might simply not need Java libraries, so you lose considerable portion of clojure benefits.

I think programs in Clojure will be measurably slower, which for some applications doesn't matter. Certainly there is a rich set of libraries and other resources available in Java.