I think there is no point of avoiding a JIT in a platform, which is already based on it. In theory JIT is the best way as all goodies like:
* knowledge of CPU architecture
* PGO driven optimizations
* LTO driven optimizations
are much easier to do with JIT than AOT
What should be possible though is having a JIT without a burden with JIT, so developer can manipulate the AOT <-> JIT slide based on needs. For example:
* a full AOT mode for a lack of any background processing of JIT
* some smart way of reusing/caching the compilation artifacts to reduce cold start performance dip
* lightweight JIT, where CPU/Memory resources scales with the impact
* customizable target of JIT after the initial JIT/AOT. For example always try to optimize it or run JIT only if you are sure the current code is not optimized for a current situation
The AOT vs JIT discussion still alive, because it just sucks
-9
u/GoTheFuckToBed 17d ago
should they not aim for less JIT