In Chrome, any JavaScript files in a service worker cache are bytecode-cached automatically.
This means there is 0 parse + compile cost for them on repeat visits.
https://v8.dev/blog/code-caching-for-devs#use-service-worker-caches …
-
Show this thread
-
Replying to @mathias
Might be worth add a note on this to Closure compiler docs. Had tried the "advanced" compilation thinking I could help v8 to parse/compile/run. But really, if chrome caches the v8-optimized code, Closure doesn't really offer much runtime assistance?
2 replies 0 retweets 0 likes -
Or maybe a section here on this: https://developers.google.com/web/fundamentals/performance/get-started/ … Web performance guidelines tend to focus on reducing payload etc, but for SPA/PWA apps I spend a lot more time thinking about how I can get my code to start&run faster _after_ downloading...
1 reply 0 retweets 0 likes
Reducing payload size helps with download time, parse/compile, and (generally) with execution time too. The fastest code is the code you don’t ship!
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.