Sure and I specifically mentioned native compilation as a recent shift for Java and C#. But that is not what the Java ecosystem and tooling got built around.

The language features that people use today are heavily dependent on it not being native code. All sorts of Java libraries are not distributed as native code and Java to my knowledge has no native ABI which can express the full feature set of Java.

Hence native AOT compilation is not some kind of drop in replacement for JIT compilation. You cannot use the same workflow and tooling you may be used to.

How a language ecosystem has been built up from the start matters. Languages designed with the intention of being used for native ahead of time compilation will naturally do a better job at it. The reverse is also true. Try sticking C++ on the JVM. Will likely not be a fun endeavor.