3 ms·
Thanks! Yes, probably doing this incrementally (or at least as separately from "user land" as possible) would have been much better. Though, this gives full p
by pas 10y ago
Thanks!
Yes, probably doing this incrementally (or at least as separately from "user land" as possible) would have been much better.
Though, this gives full program optimization via jlink, and probably modularizing rt.jar would have needed serious platform/syntax changes anyway.
What would you prefer instead?
- karianna 10y agoI'll prefix this with "I'm not a language design or modularity design expert". I personally would have preferred that JPMS was treated as an internal JVM/API concern. This still would have meant changes for IDE and tools vendors (rt.jar going away required rework for sure) but would have given more flexible options for a user space modular system to be build on top. An example is that the Module definition file (Module-info.java) is in Java source code. Despite the compile time benefits (performance, security etc) this brings, it really locks down how user level module systems need to interact with this. I personally would have gone for a straight XML/JSON/Manifest.MF/YAML/Whatever format which wasn't tied to the Java compiler so tightly.