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.
[1] http://mail.openjdk.java.net/pipermail/mlvm-dev/2014-August/005890.html
_______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
