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 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
[–] 2 points 3 years ago (1 child)

This is not true. See above.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -4 points 3 years ago (1 child)

    It IS true! See the above indeed. In short - there's no Java anything during runtime and never was.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [B] 1 point 3 years ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -4 points 3 years 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.

  • permalink
  • fedilink
  • source
  • parent