Apple

17504 readers

85 users here now

Welcome

to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!

Rules:

No NSFW Content
No Hate Speech or Personal Attacks
No Ads / Spamming
Self promotion is only allowed in the pinned monthly thread

Lemmy Code of Conduct

Communities of Interest:

Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple

Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode

Community banner courtesy of u/Antsomnia.

founded 1 year ago

MODERATORS

MichelleG@lemmy.world

RoyalEngineering@lemmy.world

thisisdee@lemmy.world

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 1 year ago* (last edited 1 year 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

you are viewing a single comment's thread
view the rest of the comments

[–] fartsparkles@sh.itjust.works 8 points 1 year ago (1 children)

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 7 points 1 year ago (1 children)

@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.

[–] fartsparkles@sh.itjust.works 1 points 1 year ago

Thank you for the insight!