Re:Clojure 1.3 First Impression (It's Fast)
by lukev on Thursday September 30, 2010 @10:56AM
(#1743458)
There is a large class of problems that aren't worth writing in assembly but for which Clojure is (currently) still too slow.
Sometimes you just need something at Java's (or preferably Scala's) position on the power/performance spectrum.
That said, the way Clojure is improving, I think it will continue to asymptotically approach Java's speed anyway.
I think the history of production oriented PLs has revolved around balancing correctness/performance. And it's always a question of diminishing return (I've written enough C/C++/Objective-C++ to know this). Every sizeable application I've written in a lower level language eventually approaches some kind of wacky manual memory management scheme to preserve performance w/o sacrificing correctness. I think Clojure's solution is a step in the right direction.
But no, if I was writing a real-time system with extremely limited memory constraints I would not write in the Clojure. But I don't think that's what this thread is about.