5 ms·
Some context: https://mail.openjdk.org/pipermail/discuss/2020-April/005429.html https://mail.openjdk.org/pipermail/discuss/2020-April/005429... Earlier design
by wavemode 3y ago
Some context:
https://mail.openjdk.org/pipermail/discuss/2020-April/005429.html https://mail.openjdk.org/pipermail/discuss/2020-April/005429...
Earlier design notes:
https://openjdk.org/projects/leyden/notes/01-beginnings https://openjdk.org/projects/leyden/notes/01-beginnings
https://openjdk.org/projects/leyden/notes/02-shift-and-constrain https://openjdk.org/projects/leyden/notes/02-shift-and-const...
- slowmovintarget 3y agoThe end result of all of this would be to allow Java-based programs to be packaged as static standalone executables. Java apps wouldn't have to "warm up."
- eikenberry 3y agoThey should have done this 20 years ago. The JVM has always been a questionable discission.
- spockz 3y agoWe already have this capability with graalvm today. Not sure how condensors compare.
- slowmovintarget 3y ago> Project Leyden will take inspiration from past efforts to explore this space, including the GNU Compiler for Java [1] and the Native Image feature of GraalVM [2]. Leyden will add static images to the Java Platform Specification, and we expect that GraalVM will evolve to implement that Specification. Developers who use only the standard, specified static-image feature will then be able to switch with ease between Leyden (in the JDK), Native Image (in GraalVM), and whatever other conforming implementations may arise, choosing amongst tradeoffs of compile time, startup time, and image size. (From one of the links posted above)