▲ 75 ▼ Possible explanation for jank in Android as opposed to iOS (20 millisecond core ramp on ARM/Android vs 50 microseconds on Apple/iOS) (social.treehouse.systems) submitted 3 years ago* (last edited 3 years ago) by octalfudge@lemmy.world to c/apple_enthusiast@lemmy.world 27 comments fedilink hide all child comments More useful context: https://social.treehouse.systems/@chadmed/110874563649736382
[–] fartsparkles@sh.itjust.works 8 points 3 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] saua@troet.cafe 7 points 3 years ago (1 child) @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. permalink fedilink source parent hideshow 2 child comments replies: [–] fartsparkles@sh.itjust.works 1 point 3 years ago Thank you for the insight! permalink fedilink source parent
[–] saua@troet.cafe 7 points 3 years ago (1 child) @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. permalink fedilink source parent hideshow 2 child comments replies: [–] fartsparkles@sh.itjust.works 1 point 3 years ago Thank you for the insight! permalink fedilink source parent
[–] fartsparkles@sh.itjust.works 1 point 3 years ago Thank you for the insight! permalink fedilink source parent