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
In the very unlikely event of fetching a JS file to parse as a string would it have to fetch it again?
2 replies 0 retweets 0 likes
Replying to @Lady_Ada_King
Are you talking about fetch as string + eval? We have a different mechanism for eval, the “eval cache” which is basically bytecode caching for eval’d strings: https://cs.chromium.org/chromium/src/v8/src/compilation-cache.cc?l=275-303&rcl=8ec122ba9de3abc2480c797adb6313b23fe08e05 …
2:10 AM - 9 Apr 2019
0 replies
0 retweets
2 likes
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.