Fun to see, I literally wrote my thesis on the same subject a bunch of years ago (Sadly didn't have an excellent option like QuickJS as a base things on back th

Fun to see, I literally wrote my thesis on the same subject a bunch of years ago (Sadly didn't have an excellent option like QuickJS as a base things on back then). First off, unlike many AOT JS compilers that has gotten exposure in the past this one actually seems realistic. The performance numbers don't see overly fantastic so they actually DO seem to implement JS properly rather than some overly optimisic JS-alike thing (the fact that they have QuickJS as an underlying base is also a plus). So for porting this is probably a pretty good choice and should produce something working, the bad part is that even if performance is better than a plain interpreter it'll suffer compared to what you can get with a proper JIT unless you tune your code heavily for the constraints of a compiler like this. I hope they have some seamless option for moving code to C/C++ (so you can run some perf critical stuff in C via WASM on the web and have an easy way to move the code to regular native code on the ported platform).