3 ms·
Jazelle was for ARM, mostly to make J2EE faster. These days, it's more practical to compile all the Java to ARM when an app is installed or in the background wh
by dehrmann 6y ago
Jazelle was for ARM, mostly to make J2EE faster. These days, it's more practical to compile all the Java to ARM when an app is installed or in the background when the phone is charging. For server-side applications, you'll either use Graal, or just live with slow-ish startup times and let the JIT warm up.
- pjmlp 6y agoSince around 2000 there has been support for AOT in Java commercial JDKs, or JIT caches across execution runs. So living with slow-ish startup times and let the JIT warm up was mostly a matter for those not wanting to shell out money for them. Actually, most likely Graal Community edition and its integration in OpenJDK, alongside AppCDS (from J/Rockit), while IBM also brought their AOT/JIT tooling into OpenJ9 that made Excelsior JET decide it wasn't worth any longer. So besides the BEA, Oracle, IBM commercial compilers now turned into free beer, PTC, Aicas are the surviving ones, but they target embedded scenarios. And then there is Android Java with JIT/AOT as well.