> But the other approach, of writing a custom JIT for each language, seems much more flexible even if it is more dangerous and time-consuming. This is also a g

> But the other approach, of writing a custom JIT for each language, seems much more flexible even if it is more dangerous and time-consuming. This is also a good illustration of how we ended up with the NULL problem. I don't think it's as big of a deal in this case as interpreters/vms/compilers are designed to be fungible in ways that source code was not, but it's something worth thinking on.