JavaScript code is much more expensive, byte for byte, than an image, because of the time spent parsing and compiling it. It's possible to parse and compile wasm as fast as it comes over the network, which makes it much more like an image than JavaScript code. Game changer!
-
-
Indeed. I'm curious to see to what degree WASM can do better here in practice :)
-
At least in Firefox (today), wasm can finish compiling and be ready to execute by the time it finishes streaming the bytes. I expect this to be possible in all browsers once competitive pressure steps up.
-
I want to add this capability to JS as well with binary AST.
-
Do you think this is a likely outcome of binary-ast? If so, can we find a way to ship in FF and put the pressure on?
-
Streaming per-function parsing and bytecode compilation is an explicit goal. Streaming interpretation is harder and I think unlikely to happen. As for landing initial prototype so we can iterate more,
@ImYoric is working hard on that.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.