The blog post about BinaryAST, which I've been working on during the last 6 months at @Cloudflare, is finally out. There is still lots of measurement and research to do, but I'm optimistic and happy about being able to be part of this story.https://blog.cloudflare.com/binary-ast/
-
Show this thread
-
Replying to @RReverser @Cloudflare
How do other browsers fare in that example you show side-by-side?
1 reply 0 retweets 3 likes -
Replying to @tverwaes @Cloudflare
I tried to be careful *not* to do that :) This must not feel like a comparison between different engines / browsers, which would would be pointless and unfair as implementations even for the same format (raw JS) differ wildly, and I wouldn't want to post misleading comparisons.
1 reply 0 retweets 2 likes -
Instead, this simply tries to visualise how much more we can potentially squeeze from semantically same JavaScript file on the same engine. As mentioned above, there is much more work on the format as well as measurements to do before going further.
2 replies 0 retweets 0 likes
Agreed that it’s not about comparing browsers. Instead, the goal is to express the overall benefit of Binary AST *across the board*, and not by comparing it to the JS parsing cost in any one particular engine. Other browsers get different numbers for the “JavaScript” column:pic.twitter.com/oUjVs21N4B
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.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.