> I can get better performance and understand my app better than with the JVM because it’s compiled ahead of time
Ahead-of-time compilation does not mean better performance.
Java HotSpot has a history of outperforming .Net, despite the latter using ahead-of-time compilation.
Similarly, various JVMs use ahead-of-time compilation, but are generally unable to outperform HotSpot.
Java's performance pitfalls are in areas like its slow reflection (or rather, in the way reflection is overused in Java libraries), its costly runtime checks for null and out-of-bounds array access, and boxing of primitive types.
Ahead-of-time compilation does not mean better performance.
Java HotSpot has a history of outperforming .Net, despite the latter using ahead-of-time compilation.
Similarly, various JVMs use ahead-of-time compilation, but are generally unable to outperform HotSpot.
Java's performance pitfalls are in areas like its slow reflection (or rather, in the way reflection is overused in Java libraries), its costly runtime checks for null and out-of-bounds array access, and boxing of primitive types.