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!
-
-
Interested: what’s bad about v8’s wasm? And do@you think there’s a good wasm engine?
-
I think FF nightly is leading the pack atm. But competitive pressure is strong and things change all the time.
-
Firefox is focusing on compiling realtime, multi-tier and streamlining wasm->js chatty situation (very fast calls across the boundary). All of these are adding up fast for my use cases.
-
Interesting! I’ve been running tests on calls abroad the boundary and not seeing great results from FF, but I’m not trying nightly. Something more to play with! Yay!
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.