Valid points, but this doesn't mean JIT doesn't work for relatively lower-latency coding.

To avoid the compilation etc. hit, common practice is to do some "warmups" before serving users. (Another reply has other ways to avoid this hit.)

Handling exceptions is higher latency, but they can/should be optimized out, so you're not hitting exceptions as part of your standard workflow (or even your 1% workflow).

> If low latency is your goal than you don't want JIT. JIT has two issues in low latency...

There's startup "AOT cache" via Leyden that speeds up startup. Isn't native speed up it's quite a big boost.

Then there's GraalVM that does give you a native image. Real AOT.