Ah. So you propose writing a Javascript compiler that spits out a dynamically linkable, PIC executable for multiple architectures using semi-static assembly, and then using that to write V8? Otherwise, if you simply dump a raw image you've got a closed environment that can't really be integrated into a browser very well, or linked into other apps for their use.

That's a whole lot of unnecessary -- and nontrivial -- work, when all you want to do is interpret Javascript.

I'm not really proposing anything, since the V8 team has forgotten more about VMs than I know, just pointing out another common design alternative. The post implies that V8 can already perform some sort of AOT compilation:

When you build V8 from source, you can have it generate a snapshot of the memory state once the libraries are loaded and this gets packaged in the executable. It makes it slightly bigger but the load time is blazingly fast.

There's certainly extra work in this approach, but maybe it would be worth it if it allows the compiler to be written in a more productive language.