4 ms·
The trouble with Clojure in my opinion is the slow JVM warmup, especially when writing small command line tools in Clojure, it's a real pain in the ass to run
by djhworld 14y ago
The trouble with Clojure in my opinion is the slow JVM warmup, especially when writing small command line tools in Clojure, it's a real pain in the ass to run
lein run myscript.clj
and then sit there waiting for 2 - 3 seconds to see your result. Might sound insignificant but it's noticeable when you're constantly switching between source and result. Obviously the way to get around this is to load everything into a REPL and enjoy the advantages of explorative programming.
This is where Haskell has an advantage, the runghc command is very fast, and compiling your script/program into a static binary means it's quick to execute as well.
Clojure (and Scala) need to sort out the JVM warmup to make them viable general purpose languages.
The bizarre thing is, running Java on the JVM startsup almost instantly.
- douglasisshiny 14y agoYeah, I've been reading about clojure's performance a bit today -- the slow JVM startup is mentioned a bunch. I've been reading that it's not always trivial to get clojure to perform on par with java itself. From a web application background, are performance gains seen because of clojure's concurrency?