Guys, Move This to the Background
summary
A service-worker–based image cache sits in front of Google Drive fetches to speed up client-side image processing, reducing perceived load from ~1s to ~20ms (~50×). It uses service workers for offline assets, font bundling, custom cache strategies, background sync and push, and includes a deployed proof‑of‑concept that avoids main‑thread stalls from long scripts; currently experimental in Chrome (flag) and Chrome for Android with unclear per‑origin cache quotas.
AI-written summary · about
chapters (15)
- 0:00Background processing
- 1:03Heavy scripts in browser
- 3:33Service Workers benefits
- 5:41Faster image loading
- 8:37Caching fonts offline
- 11:53Cache management
- 14:06Data storage limits
- 15:52Push notifications background
- 18:17Service Workers security
- 21:07Background mining risks
- 23:41Service Workers incognito
- 24:50Service Workers lifecycle
- 25:54Testing future support
- 27:43Version updates persistence
- 29:31Q&A
related talks
27m"WASM: Bringing Go to the Browser (and Beyond!)"
46mSimplifying Scalable Cloud Application Development with Go
37mHow I made a powerful cache system using Go
06mInterview – John Graham Cumming
31mHow Go is Making us Faster
17mHow we built and launched Gopherize.me
27mTowards Modern Development of Cloud Applications
04mHandling slow requests in your Go web server