Clojure on JVM
Users discuss Clojure's strengths including seamless JVM integration, superior productivity over Java, Lisp features, and comparisons to Common Lisp, Scala, and Haskell, often defending it against criticisms of failure or niche status.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Disclaimer: Amateur's blundering travelog.I've been dabbling in Clojure for about 4 years now, off and on, and it works very well for small-ish projects. The integration, as others have mentioned, with the JVM is superbly seamless (it leaves Scala in the dust in this respect) and this opens up most of the Java ecosystem. Also, the STM model of concurrency management is super cool. So far so great!But every time I try to build something more substantial than a Project Euler submis
Why do you consider Clojure a failure in the Java ecosystem?
I used CL as a hobbiest for years but never in code I would get paid for. Clojure is a different story. That you can run it on the JVM is a game changer when you want to introduce the code to a production environment. The massive amount of Java libraries and tooling plus the operational knowledge that organizations have make it a much easier sell even with "all those rackets". More language related reasons I prefer it to Common Lisp are things the syntax for vectors, maps and sets that
Clojure is a LISP and from my experience I'm way faster with Clojure than with Java. Plus Clojure can use any java library. And by the way it seems that you have never used any lisp for web development. When you bump into the first problem with the bloatware made of 30.000 files and you have to debug it because there were no answers on stackoverflow...then you will find all out about the dark sides of "advanced frameworks".
Clojure is the default go to language for me over the last 5 years. It is not even funny how more productive Clojure is compare to Java if we are talking about JVM hosted languages. There are obviously shortcomings of Clojure, missing Either and so on, but you can always implement these simply, worst case with a macro. It is good to see libraries like cats though.
Clojure does not look like C and requires some pretty tough mind-bending, especially if you have been programming for 30+ years like I did when I started. Still, more people use it than Haskell. But it has an enterprise-friendly environment (all Java or JS libraries, or both) and a super-friendly community.
I think the problem with Clojure is that it does not translate to Lisp 1 for 1 or rather the other way, Clojure relies on many of the Java libs and therefore requires some mastery of the Java API's this does not translate over to other lisps. That being said, the Clojure market is small but healthy, I have received several job offers for Clojure development in the past few months which would have been unheard of a year ago. Clojure is growing rapidly from my perspective and will continue to do s
I did clojure as a hobbyist for years and have only recently taken a job where I'm working full time in Clojure on a large codebase (i.e., first time having to maintain somebody else's Clojure code). It's not a golden hammer by any means, but I'd definitely take it over Java (or Scala) any day.
I use CL and am currently learning Clojure. I think there are generally more libraries for Clojure and better communities (in some way). Maybe it's due to the JVM, I dunno.
As a polyglot dev with experience in JS, Python, Scala, Clojure, Java to name a few, Clojure is hands down in another league compared to all the rest. My experience is with Clojure is my productivity is a magnitude higher next to others. The REPL and instant feedback alone propel develoment velocity and developer satisfaction so far out there there is just no contest.