And yet, JEP 161 addresses the most pressing requirement from Java developers: a smaller, more embeddable JRE.
Furthermore it actually seems to be deliverable within a reasonable time scale (JDK8) rather than a continually slipping, indeterminate future. - Neil On Wed, Sep 4, 2013 at 11:35 PM, <[email protected]> wrote: > 2013/8/30 0:35 -0700, [email protected]: >> My understanding is that JEP 161 (http://openjdk.java.net/jeps/161) already >> addresses many requirements for modularizing the Java runtime. JEP 161 >> should address the concerns around creating a scalable platform and improve >> performance. >> >> I would like to understand what requirements in addition to JEP 161 this >> prototype aims to address. > > JEP 161 is an interim solution to the problem of scaling the platform. > It "modularizes" the platform in only the crudest sense, defining just > three modules. If an application uses just one API from the largest > profile and otherwise requires only the smallest profile then there is > no choice but to use an implementation of the largest profile. > > As to performance, JEP 161 doesn't address that at all. The kinds of > performance improvements we've always aimed to enable with Jigsaw > involve transforming module content during installation. > > - Mark
