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!
-
-
I think people expect that "if the wasm is 2x bigger than the JS, game over". That is not actually true on a good wasm implementation. (note: today's v8 is not a good wasm implementation, but it will be before too long, I hope)
-
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 -
-
-
I am using wasm-gc; it’s very cool! Even so, there are cases in my microbenchmarks where wasm ends up wayyyy bigger (like 300x) because of stdlib. But as
@_jayphelps points out, in a large the stdlib probably gets amortized. And I do wonder how binary-ast will change things. -
Another factor: rust hasn't quite gotten its wasm ecosystem revved up. It already has a decent no_std ecosystem but we need a lot more to make things nice and small for wasm. High priority for early 2018 for us.
End of conversation
New conversation -
-
-
That's complete fake. Well designed pages don't spend enough time in "parsing" phase to make noticeable difference. Majority of modern page waste comes from having too many requests per page (yes, including images), and too massive assets (yes, images).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.