On 12 dec, 17:29, Sean Devlin <francoisdev...@gmail.com> wrote: > First, is the STM. This is THE killer feature of the language. > Ironically, it gives Clojure its identity, and ridiculously clean > design. Write a concurrent app with it and you'll see.
For me, it's not even the STM that's so compelling about clojure - it's a cool feature that I've personally not used that much yet, being a fairly recent "convert". What I like about clojure most is the "ridiculously clean design" of the collection types, and the way it encourages pure-functional programming without it feeling forced. It easily kicks the ass of every other Lisp I've seen. I like Lisp, but in Common Lisp and Scheme all the collection types other than lists seem "bolted on". Clojure is the first programming language (not just Lisp variant) I've seen that offers a such a clean & consistent way of dealing with maps, lists, vectors etc. If I had to offer critisisms of clojure pretty much all of it is due to the JVM; off the top of my head: lack of optimized tail-calls and threads being too expensive (I really think Erlang does this much better) at the most annoying. Personally, I think the whole built-on- Java thing is OK but not great, it's good to have an alternative when there is no clojure library for *insert problem here*, and it probably helps adoption of clojure in "enterprisy" environments, but that's about it as far as I'm concerned - I certainly do not see clojure as a "better Java". Cheers, Joost Diepenmaat - who's done Java, and didn't like it much. -- 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 Note that posts from new members are moderated - please be patient with your first post. 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
