Interesting approach using a JIT compiler. It says compilation is slow, is there a way to persist the compiled code and load it later (for example for CLIs or faster redeployments)?
The key feature seems to be the dynamic nature while still being fast. Sure, they could also build it as a compiler that does all mentioned in the article and then dump optimized Go code. Maybe even use the Go PGO instead of their own. But this is another approach, what I mean is caching of the JIT generated code to avoid doing expensive part again while still being dynamic and adapt to incoming messages.