@mathias remember our recent "debate" about whether people still in 2019 think of JS parsing times as being a bottleneck?
https://blog.cloudflare.com/binary-ast/
Seems like this is still very much an issue with a fair bit of attention.
-
-
They awknowledge in the article that parsing in v8 has dramatically improved lately. Anyway, my point then, and now, is not that JS parsing is slow, but that it's still an issue people care about and that is still motivating projects/experiments. It's not a moot/settled issue.
-
Oh, people are definitely experimenting (the Binary AST proposal being one example). In fact, I’m super glad
@RReverser and@Cloudflare are helping explore this space through their research, and I wholeheartedly agree with their goal:pic.twitter.com/4F2vjvLj0Y
End of conversation
New conversation -
-
-
To clarify my earlier statement, it looks like there’s still room for improvement in Firefox (the browser tested in the article) w.r.t. raw parse cost, and I’d love to see wins there as much as anyone. I’m just personally not convinced we need Binary AST to get there.
-
We can all agree that startup cost is a problem. In modern Chrome, parse cost is not the dominating factor however — download+execution are! This (to me) indicates that even without a new standard such as Binary AST, browsers can still improve.
- 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.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.