In particular, the attached comment noting that JITting is the basis of our modern CPUs is poignant when we consider that it is to GPUs that we look for top performance, nowadays. While those are programmed via compilation-at-runtime, for historical reasons, there is no attempt at interpretation or runtime analysis; regular AOT code is compiled, typically at startup, and run natively. The execution model is such that tricky optimizations are not needed to get maximum performance (so compilation can be quick); instead, the key is to always have plenty of other work to do during what would otherwise be stalls, relying on what amounts to massive hyperthreading.

Massive hyperthreading is another dynamic, runtime allocation of resources, but of a wholly different order than JITting. In particular, it has no concept of data type operated on being unknown until runtime, although vtable-style late binding, dispatching according to specific, known types, works.