most of those are (no criticism of post intended) as much about fp as clojure. intellij/idea + la clojure plugin wasn't mentioned, but is also a pretty good en

most of those are (no criticism of post intended) as much about fp as clojure. intellij/idea + la clojure plugin wasn't mentioned, but is also a pretty good environment (however, i am seriously annoyed that the c/c++ plugin is dead - how can a major ide ignore c?!). and i second the problems with profiling (see http://stackoverflow.com/questions/7223297/please-help-me-understand-these-clojure-hprof-traces http://stackoverflow.com/questions/7223297/please-help-me-un...) - traces don't help much at all, but you can force critical chunks of code to java-like speed with some effort. one thing that i don't think was mentioned is that the language (+ libraries) was changing pretty quickly not so long ago. i am not sure if it's stabilised "forever", or if 1.4 was just an exception, but 1.3 to 1.4 has been less traumatic than previous releases. also, while i'm at it, it's probably worth emphasizing the two things that clojure has that you wouldn't expect from just "java + fp". first, the lazy sequences are great. imho this buys you some of the flexibility of haskell without the "other stuff". it was always possible in other languages, of course, but clojure makes it the new normal, and it's great. second, the multithreading support (not just the lack of state, but the transactional mem stuff). in both cases, it's like "haskell for normals" :o) (and in haskell's defense, perhaps explicit types would help with some of the design / architectural issues mentioned in the article once you start using hofs).