Java app developers, protect your intellectual property and improve the end-user experience. Get Excelsior JET.
 

Video: Nikita Lipsky Talks About Java AOT Compilation @GeekOut 2016

This post is now superseded by “Video: Nikita Lipsky Talks About Java AOT Compilation @JavaZone 2016“, where the quality of the talk is better.

Categories: Java

6 Responses

  1. Roedy Green Says:

    I have been using Jet for a number of years now, so this lecture covered things I already knew. It would be nice to hear a lecture aimed at people like me.

  2. Roedy Green Says:

    AOT has two problems with running on handheld devices.
    1. handhelds are usually strangled for RAM. AOT gobbles RAM.
    2. AOT brings the needed library code embedded in each app. This means fitting two apps in RAM at a time is a problem. With JIT you share the library. You might have a staticallly compiled shared JVM.

    Finally you chew up way more bandwidth downloading AOT apps.

  3. Roedy Green Says:

    Any hope of a common statically compiled JVM that a dozen Jet apps share, just that way you can on development machines? I want to shrink the downloads.

  4. Dmitry Leskov Says:

    > Any hope of a common statically compiled JVM that a dozen Jet apps share, just that way you can on development machines? I want to shrink the downloads.

    JetPackII supported packaging multiple executables with one runtime since forever.

  5. Dmitry Leskov Says:

    > AOT brings the needed library code embedded in each app. This means fitting two apps in RAM at a time is a problem. With JIT you share the library. You might have a staticallly compiled shared JVM.

    iOS apps are self-contained. There is no way they could share a JVM unless Apple built one into the platform. Ditto for libraries.

  6. Dmitry Leskov Says:

    > It would be nice to hear a lecture aimed at people like me.

    We have a couple of more in-depth videos, but, unfortunately, they are in Russian.