News for hackers. Stuff that matters.
Re:JEP 295: Ahead-of-Time Compilation by the8472 on Thursday October 27, 2016 @04:50PM (#12809950)
> No dynamic byte code (Lambda Expressions, Dynamic Classes, etc.)

That just means it won't be AOT compiled. The JVM can still JIT them.

> No decrease to JVM start up times

The JVM itself starts quite fast. Most of the time spent in startup comes from the applications themselves. Spend a lot of time in the interpreter running their startup code and burning CPU cycles on the lower compiler tiers.

> The only supported module is java.base

Supported in the sense of oracle offering support. You can still compile other modules. It's just experimental.

Re:JEP 295: Ahead-of-Time Compilation by bluejekyll on Thursday October 27, 2016 @06:25PM (#12810875)
> The JVM itself starts quite fast. Most of the time spent in startup comes from the applications themselves.

Jar unpacking can contribute quite a bit to startup times. It would be neat if this also did a pre-linked library as well.

Re:JEP 295: Ahead-of-Time Compilation by lern_too_spel on Thursday October 27, 2016 @07:00PM (#12811176)
An optional link step at build time is coming in Java 9. http://openjdk.java.net/jeps/282
Re:JEP 295: Ahead-of-Time Compilation by paulddraper on Thursday October 27, 2016 @09:12PM (#12812088)
So if you use .class files instead of .jar files, you'll start up significantly quicker?
Re:JEP 295: Ahead-of-Time Compilation by bluejekyll on Friday October 28, 2016 @10:54AM (#12816477)
Yes. In fact many systems unpack jars to a temporary directory first for this reason.

edit: I should add that this really only matters for large numbers and sizes of jars.