Forget Go. Go, Java, go!
summary
GraalVM’s Substrate VM and native-image compile JVM apps ahead-of-time into single self-contained executables (Linux/macOS; Windows preview) that start instantly and use far less memory. Demo: Sieve of Eratosthenes — Go exe ~2 MB / 260 ms, JVM on HotSpot <100 ms, native-image exe <3 MB. Interop demo: naïve JNI matrix access takes ~5 s, moving the algorithm into a native-image library drops it to 70 ms (≈60× faster). Limitations: not full TCK, reflection config required, ARM support in progress.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:54The Practical Api Design Book
- 2:51Introduce Go Language
- 7:12Turing Speed
- 7:34Infinite Memory
- 8:43Go Language
- 10:58Can Java Do Better
- 12:53Why Not Stick with Java
- 20:24Demo of How To Change My My Program and How To Compile It
- 24:17Does Gravel Vm Do the Same Optimization as Hotspot Jvm Is There a Jit Compiler
- 25:25What about Dynamic Class Loading
- 26:29Can You Choose Different Garbage Collector after Native Code Has Been Compiled
- 27:09Why the Algorithm Is Running Slow
- 28:43Is It Possible To Create Executable for Arma
- 32:33Inter Connecting jvm the Classical Jvm with Native Code
- 34:52Gnu Scientific Library
- 47:03What Are the Known Limitation Regarding Which Apps Can Be Compiled into Native Image
related talks
44mJava In The Cloud with GraalVM
42mJava in the Cloud with GraalVM
52mGraalVM native images explained
31mGraalVM native images explained
49mBuilding native images for fun and profit
47mBring the action: using GraalVM in production
49mGraalVM: Run Programs Faster Anywhere
44mSelf-contained Native Binaries for Java with GraalVM
