What's your point? This is what the regular JVM/HotSpot has been doing for ages (and GraalVM, too). Whereas native-image does AOT, with optional profile-guided optimization to identify hotspots on the fly.
Apparently I left out a line break. It should read
> this is a huge downside.
The compiler can only do static analysis and code generation. I'd much rather a hotspot VM analyze the running code and identify the optimizations on the fly.
So I believe we're in agreement, that AOT imposes does limited optimizations compared to HotSpot JIT
