News for hackers. Stuff that matters.
Re:Ahead-of-Time Compilation by paukiatwee on Saturday October 01, 2016 @12:45AM (#12616545)
Java AOT is compile JVM bytecode to native code during startup of JVM, which is different from Go's compile source to native and distribute platform specific binaries. So in this case, Java binary size remain same as before, which is .jar or .war binaries.

For Go, .go -> native

For Java, .java -> .class -> package .jar -> AOT native

For Go part I might be wrong, not working on Go professionally.

Re:Ahead-of-Time Compilation by mike_hearn on Saturday October 01, 2016 @06:47AM (#12617327)
No, not during startup, AOT can happen at any time chosen by the developer or user: there's a command line tool that triggers it and I believe the plan is to integrate it with the "jlink" tool that produces standalone, app specific JRE images. So you can produce a native installer for each platform.
Re:Ahead-of-Time Compilation by Scarbutt on Saturday October 01, 2016 @01:26AM (#12616621)
My understanding is that JVM bytecode is compiled to native before startup of the JVM, that is why it is called AOT ;)
Re:Ahead-of-Time Compilation by sandGorgon on Saturday October 01, 2016 @01:21AM (#12616613)
that is an incorrect assumption. AOT step will include deadcode elimination. In that way - the Java way is a more sophisticated way combining platform independent bytecode and platform-specific machine code.
Re:Ahead-of-Time Compilation by bitmapbrother on Saturday October 01, 2016 @03:22AM (#12616881)
No it's not. Compilers such as the one in IBM's J9 have a switch setting to use AOT.