• Sheltac@lemmy.world
    link
    fedilink
    arrow-up
    21
    arrow-down
    1
    ·
    1 year ago

    Wait, thats is very different from what I read back in the day. I know there was a point at, I dunno, android 5 where they started doing something different with java, but my impression was that android always ran a JVM of sorts. And frankly, given how it performs even on the highest-end devices, that was really easy to believe.

    I guess I need to do some research now.

    • bluefirex@lemmy.world
      link
      fedilink
      arrow-up
      37
      arrow-down
      1
      ·
      1 year ago

      No you’re correct. Android does run a JVM, just not Oracle’s. That has always been the case. Back in the day it was Dalvik, nowadays it’s ART.

    • fartsparkles@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      1
      ·
      1 year ago

      Pretty sure it was Dalvik virtual machine that Java was compiled to byte code for before 4.4 when they deprecated Dalvik for Android Runtime (ART), fully dropping Dalvik in 5.

      • saua@troet.cafe
        link
        fedilink
        arrow-up
        7
        ·
        1 year ago

        @fartsparkles @Sheltac Android always ran dalvik bytecode and never Java bytecode
        The change to Art was just a replacement of the “VM”, but didn’t change what byte code was run. It’s similar to how Hotspot improved the Java VM while also not fundamentally changing that it’s running Java bytecode.