The JVM class loader by default reads a class on first reference to it in the code it's executing. Never refer to it, never gets loaded.
Startup on the JVM is more affected by the JIT warming up, and the heap getting into a "stable" configuration.
Re:Windows 10 and .NET Native
by jacques_chester on Saturday October 03, 2015 @01:47PM
(#10324677)
Thanks for the correction.
Java 9's module system should make that a lot less of a problem by giving the JVM guidance on what it should load and skip.
I am not a Java expert, though, so I may have misunderstood what's going on.