Personally, I dislike LISP odd syntax, the widespread use of side effects in
a functional language and the poor abstraction that lists represent over RAM,
from a performance point of view β indeed LISP variants often add additional
data structures, somehow negating the βLISβ part of the language. In the
specific case of Clojure, the fact that a compiled language is compiled into
an interpreted one, JVM bytecode, combining a slow dev cycle with suboptimal
performance, makes me think Clojure users must be glutton for punishment.
Clojure has sophisticated state management. So much for widespread use of side effects.
Clojure has high performance data structure implementations tuned for modern hardware. So much for performance.
Clojure is compiled on the fly at the REPL and the JVM is one the fastest runtimes out there. So much for slow dev cycle.
You may not like the syntax, but boy is that Hadoop query short and sweet.
Yeah it's almost hilarious how every critic he is aiming at LISP is fixed in Clojure, where immutable is the default and vector the data structure of choice. Also he clearly doesn't understand the subtleties/differences between compilation and interpretation, and how the two can interlace.
Clojure has sophisticated state management. So much for widespread use of side effects.
Clojure has high performance data structure implementations tuned for modern hardware. So much for performance.
Clojure is compiled on the fly at the REPL and the JVM is one the fastest runtimes out there. So much for slow dev cycle.
You may not like the syntax, but boy is that Hadoop query short and sweet.