Top 3 Browser Features Wishlist for React: 1. Service Worker Cache 2. Persistent Bytecode/JIT Cache Preparsed in SW 3. requestIdleCallback
-
-
Replying to @sebmarkbage
what does Cache give you that IDB doesn't? same for rIC vs setImmediate?
1 reply 0 retweets 0 likes -
Replying to @patrickkettner
It can update in the background while not on the page and the JS cache can include bytecode/JIT (2) if the browser knows.
2 replies 0 retweets 1 like -
Replying to @sebmarkbage
so less service worker cache than background sync, no?
1 reply 0 retweets 0 likes -
Replying to @patrickkettner
Well the most important part is step 2. Ability to have JS preparsed into VM specific bytecode *before* the page loads.
2 replies 0 retweets 1 like -
Replying to @sebmarkbage
: sorry for slow reply; aggressive caching of parsed scripts is looking good in our field trials
1 reply 0 retweets 1 like -
Replying to @slightlylate @sebmarkbage
: you'll get roughly this behaviour for re-used SW-cached script soon. Next up: as soon as you put in SW cache.
1 reply 0 retweets 4 likes -
Replying to @slightlylate @sebmarkbage
: of you use offline-first architecture w/ that, you get effectively what you are asking for
1 reply 0 retweets 1 like -
Replying to @slightlylate @sebmarkbage
: a question of timelines now; interpreter will launch soon and will change the dynamics a bit
2 replies 0 retweets 1 like -
with 3+ pushes a day, how much value would a JS bytecode cache have?
1 reply 0 retweets 0 likes
: TONS. If you download new versions in bg w/ SW update, can always be fast
-
-
but the field trail you mentioned didn't involve SW byte code caching, right?
1 reply 0 retweets 0 likes -
Replying to @digitarald
: we cache a side-structure of parsed script. Not bytecode (but will be when Ignition ships) /cc
@sebmarkbage@patrickkettner0 replies 0 retweets 0 likes
End of conversation
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.