But wasm is not really JavaScript :( Would be nice to have a JavaScript bytecode with those good properties.
In particular: - the spec is already designed to evoke an AST - hiperf comes from later tiers - the JS compiler ecosystem has actively worked on some standardization - this problem wasn't a high order bit objection in TC39 when it came up (vs prioritization and "is it worth it")
-
-
I could be wrong about any of these assumptions, but I think the wins of binary are so large, that if we could get everyone to agree with the benefits, there'd be strong motivation to make it work. Cutting http://facebook.com parse time by 8x is no small thing.
-
Oh and I meant to say: Because of the likely debate around trying to standardize a whole new AST (both from impl and other stakeholders) the path of least resistance is to stick closely to the spec's representations at first. I think this is a good thing
- 1 more reply
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.