4 ms·

> it reduces the startup time and memory footprint of the JVM How so? There is additional machinery needed to be started, the module system, and additional che

> it reduces the startup time and memory footprint of the JVM How so? There is additional machinery needed to be started, the module system, and additional checks needed to be performed (module access) and additional metadata to be kept at runtime (module metadata). How is that helping startup time and and footprint? If anything that should make it worse. Class loading has been lazy since day one, so if you don't use CORBA then CORBA classes are not loaded. This has been the case since Java 1.0. JVM startup time is actually pretty good. If your application takes seconds to start that's because your startup code takes seconds to run. Jigsaw isn't going to help you there.

pjmlp 9y ago
Module system supports linking, it is possible to create a JRE for distribution having only the code that actually matters for the application. It is also part of how the upcoming AOT compiler to native code will work.
- needusername 9y ago
  > Module system supports linking Nope, that's an entirely proprietary, intentionally unspecified extension. > it is possible to create a JRE for distribution having only the code that actually matters for the application. I don't see how this reduces the startup time and memory footprint of the JVM. If a class is not needed by your application it's not loaded, that has been the case since Java 1.0. I don't see how it not being present on disk makes any difference. > It is also part of how the upcoming AOT compiler to native code will work. Nope. It also works on classes and plain old JARs [1] [1] http://openjdk.java.net/jeps/295 http://openjdk.java.net/jeps/295