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/
Android doesn’t use Java at a byte-code level and never has, as far as I can tell. Source code was written in Java since mobile developers were so used to it but Android never ran the JVM, they do their own thing with Java source.
You can dislike Java syntax but the software stack on Android wasn’t Java’s.
Wait, thats is very different from what I read back in the day. I know there was a point at, I dunno, android 5 where they started doing something different with java, but my impression was that android always ran a JVM of sorts. And frankly, given how it performs even on the highest-end devices, that was really easy to believe.
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.
@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.
They compile Java Bytecode to Dalvik Bytecode and run that on the Android Runtime which is a tiered JIT compiler.
It still inherits the issues of Java such as the GC, no stack allocated value types, poor cache locality, etc. Although tbf the GC on Android is pretty fucking good these days and doesn’t pause the world anymore.
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.
Interesting, I always thought it had to do with Android’s ungodly software stack which at some point involves, of all things, fucking java.
Android doesn’t use Java at a byte-code level and never has, as far as I can tell. Source code was written in Java since mobile developers were so used to it but Android never ran the JVM, they do their own thing with Java source.
You can dislike Java syntax but the software stack on Android wasn’t Java’s.
Wait, thats is very different from what I read back in the day. I know there was a point at, I dunno, android 5 where they started doing something different with java, but my impression was that android always ran a JVM of sorts. And frankly, given how it performs even on the highest-end devices, that was really easy to believe.
I guess I need to do some research now.
No you’re correct. Android does run a JVM, just not Oracle’s. That has always been the case. Back in the day it was Dalvik, nowadays it’s ART.
There you go, that’s exactly what I was thinking. Thanks!
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.
@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.
Thank you for the insight!
deleted by creator
They compile Java Bytecode to Dalvik Bytecode and run that on the Android Runtime which is a tiered JIT compiler.
It still inherits the issues of Java such as the GC, no stack allocated value types, poor cache locality, etc. Although tbf the GC on Android is pretty fucking good these days and doesn’t pause the world anymore.
Removed by mod
ART?
Removed by mod
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.
Removed by mod
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.
Removed by mod
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.
Thou art wrong.
This is not true. See above.
Removed by mod
How would you define what’s “Java” then. The language used by source code, or the compiled bytecode, or the runtime?
Removed by mod