The Great Startup Problem [1] was a wonderful read highlighting the
problems surrounding the early life of a JVM application. In-flight efforts
that allow (to a limited extent) better startup characteristics include
jaotc, substrateVM, jlink. These efforts all trade away dynamicity of some
sort, and dynamicity is one of the magical powers of the JVM.  What sort of
opportunities exist for improving startup that don't trade away the
capability to run indy or impose whole-program analysis? As a user of
Clojure, I value how dynamic the JVM is along several dimensions.

mlvm-dev mailing list

Reply via email to