Finally, the next version of Nucleus will be 3.0, ...
# nucleus
u
Finally, the next version of Nucleus will be 3.0, almost no breaking changes for those already on tao, but something very interesting, my JVM optimized profile consumes almost 60mb less than the native image graalvm version on my app on btop 🤯 however, in the Windows Task Manager, the JVM version remains higher than 110mb,I think I will stay on GraalVM until the introduction of openjdk.org/jeps/544, because there are some lags on the JVM version that are not present on the GraalVM version due to the compilation of elements when they appear for the first time, but this will be corrected by JEP 544. We will just have to generate the AOT cache on the host via Nucleus and not on the runner because it does not generate generic machine code. It will be a bit of a hassle, but once that is done we will have smaller binaries and even better performance without going through GraalVM! The dream, right? 🤩
Enregistrement de l'écran 2026-10-06 204655.mp4
m
What about Nucleus 2.6 before 3.0?
u
I renamed the nucleus 2.6 branch to 3.0 🙂
Since I am completely removing the awt backend, I thought that changing the version would encourage developers to read what has changed.
😉 1
m
Would you say that 3.0 dev is already as stable as 2.5.18? I need to ship an app and 3.0 dev would fix a bug for me.
u
Yes, 3.0 dev is more stable
thank you color 1