Great post. 2 Qs on the JSON perf section 1. Is pre-parse and lazy-parse the same? Pre-parse happens during lazy-parse right? 2. JSON-stringified format is faster because we are saving on parse time? But will the compile and execute time increase since we lack a proper AST?
The dominant costs of processing JavaScript are:
download
CPU execution time
@addyosmani on the cost of JavaScript in 2019: https://v8.dev/blog/cost-of-javascript-2019 …pic.twitter.com/6uF8Nmjz62
-
-
-
Pre-parse is the first pass of parsing that always needs to happen, in order to find function boundaries and variable bindings. Lazy parse happens when we actually compile functions that are compiled lazily.
- 2 more replies
New conversation -
-
-
"What does this mean for web developers? Parse & compile costs are no longer as slow as we once thought." Developers: So we can add more JS to our pages!
- 2 more replies
New conversation -
-
-
Is this just V8 stuff, or can we see this as a general recommend? If it's just V8, it might be smart to rephrase the headline to avoid confusion.
-
I view this as a general recommendation. We focus on telling the V8 story as it's what we have the most detail on, but keeping network + execution costs low should help experiences get interactive quicker in all browsers.
- 1 more reply
New conversation -
-
-
Astonishing work!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
You should mention how highly CPU utilization in chrome purposefully delays/pauses networking and makes download times longer.
-
For example, open a new tab in chrome, open devtools so you can grab the timing info, and put this in the URL bar: https://mailfoogae.appspot.com/build/app.js Now curl the same file. Download times are about 100x different.
End of conversation
New conversation -
-
Show additional replies, including those that may contain offensive content
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.