Apple

17421 readers

171 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

thisisdee@lemmy.world

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

[–] tehcpengsiudai@lemmy.world 1 points 1 year ago (1 children)

How would you define what's "Java" then. The language used by source code, or the compiled bytecode, or the runtime?

[–] Aux@lemmy.world -4 points 1 year ago

I don't define anything, there are Java standards which define source code, binary code and runtime behaviour compatibility. That makes it possible to run Java apps on non-Oracle JVMs, use non-Oracle tools, etc. Android doesn't have anything Java outside of source code. And even Java source code is not 100% compatible. It's just not Java at all and never was. You can't even use many open source Java libraries on Android because they are not Android compatible at the source level.