> There are, however, a few drawbacks to the Java virtual machine, which Clojure traditionally runs on. From my experience, many developers, fairly or not, have an issue with requiring the JVM, and shy away from Clojure because of startup time, a somewhat heavyweight runtime, and perceived bootstrapping complexity.
This used to be discussed in the past and it has been proven that the culprit is the clojure implementation itself, the work done during startup, that regular Java code doesn't do, or can even take advantage of JIT caches/AOT.
"Why Clojure starts up slowly — is it really the JVM?"
https://ericnormand.me/article/the-legend-of-long-jvm-startu...
"Clojure's slow start — what's inside?"
https://clojure-goes-fast.com/blog/clojures-slow-start
"Why is Clojure bootstrapping so slow?"
https://blog.ndk.io/clojure-bootstrapping.html
"Babashka: How GraalVM Helped Create a Fast-Starting Scripting Environment for Clojure"
https://medium.com/graalvm/babashka-how-graalvm-helped-creat...
But the myth stays, because everyone has opinions based on perception.
Anyway, great to have Jolt as an option as well.
This used to be discussed in the past and it has been proven that the culprit is the clojure implementation itself, the work done during startup, that regular Java code doesn't do, or can even take advantage of JIT caches/AOT.
"Why Clojure starts up slowly — is it really the JVM?"
https://ericnormand.me/article/the-legend-of-long-jvm-startu...
"Clojure's slow start — what's inside?"
https://clojure-goes-fast.com/blog/clojures-slow-start
"Why is Clojure bootstrapping so slow?"
https://blog.ndk.io/clojure-bootstrapping.html
"Babashka: How GraalVM Helped Create a Fast-Starting Scripting Environment for Clojure"
https://medium.com/graalvm/babashka-how-graalvm-helped-creat...
But the myth stays, because everyone has opinions based on perception.
Anyway, great to have Jolt as an option as well.