Here's my experience... I was primarily interested in Clojure as a scripting language. I wanted a nice layer to control code written in Java. I had used Groovy successfully, but missed macros and an extensible syntax. I used to work at Lisp Machines, so I jumped on a LISP that compiled to the JVM.
Unfortunately, while I love Clojure for algorithms and stretching my brain, it is not very good for scripting. This is because it is really too different from Java. Clojure programming requires that you do things the "Clojure way". Therefore, a Clojure wrapper does not map very well to a set of Java objects; calling Clojure from Java is clunky; and debugging lazy code that invokes Java is difficult. Clojure is best when everything is written in Clojure. Some day Clojure programs will be able to take advantage of parallel hardware. Then there will be a performance reason to write core algorithms in Clojure. Unfortunately Java is still significantly faster this year. So for me, Clojure is beautiful, coding is a joy, and Clojure is the future... but I can not use it for work yet. Peter --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
