Attached: 1 image
Wait, 20 *milliseconds*? Either their kernel scheduler config is completely out of whack, or ARM/Qualcomm really screwed this one up.
Apple cores can boost to max in around 50 *micro* seconds. 20 milliseconds is just broken. That's more than one frame, and that's how you get janky UI response and dropped frames. I hope this was a config issue and these cores/designs really don't take 20ms to increase clocks (I could see that with a really bad regulator/power delivery system...)
From: https://chipsandcheese.com/2023/08/11/arms-cortex-a710-winning-by-default/
ART is the equivalent of a JVM. It doesn’t implement all the apis, the compiled bytecode differs, it’s optimized for mobile but that doesn’t make it not a JVM.
That’s why the NDK exists: so you can build and run C++ code natively.
You absolutely can pull the same jars into server and android projects.
Sometimes you need a different one for Android to avoid NoClassDefFoundErrors but you’re totally able to grab a jar and stick it directly into both sides.
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.
Java is only used for software development, there’s nothing Java during run time.
ART?
ART what?
ART is the equivalent of a JVM. It doesn’t implement all the apis, the compiled bytecode differs, it’s optimized for mobile but that doesn’t make it not a JVM.
That’s why the NDK exists: so you can build and run C++ code natively.
Python VM is Java by your logic. If you don’t understand IT, you shouldn’t really talk on IT topics.
I can use the exact same apache jars on my Android project and my Java server.
That’s not Python. That’s very clearly java code.
The implementation of the contract is different but that’s not the same as not being Java.
You can’t use the same JARs in runtime.
You absolutely can pull the same jars into server and android projects.
Sometimes you need a different one for Android to avoid NoClassDefFoundErrors but you’re totally able to grab a jar and stick it directly into both sides.
The hell are you even talking about? You can’t even load a JAR file on Android. My god…
Thou art wrong.
This is not true. See above.
It IS true! See the above indeed. In short - there’s no Java anything during runtime and never was.
How would you define what’s “Java” then. The language used by source code, or the compiled bytecode, or the runtime?
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.