In the divide between AOT and JIT, and not being able to have them both, is the deoptimize question. You come back from JITted code to a specific call site; which is easily available to you if you're in an interpreter, but might have been compiled away if you're in an AOT. Plus all tricky aspects of safety, synchronization, performance associated with this.<p>From their front page, the following makes me think that they don't do AOT at all:<p>> Explore<p>> Jyt enables explorative C++ programming using a REPL.<p>> Patch<p>> Hot-swap functionality at run-time. Deploy fixes with zero down-time.