Why the little story at the beginning? Annoying and silly.
Writing a Service Worker
21–30 of 60 posts
Re: Writing a Service Worker
#22I always get all stoked on service workers until I remember that half my users are on safari. Then I get bummed.
What's the difference with Safari? (not a JS dev, so this is not familiar territory)
Re: Writing a Service Worker
#2320 lines of JS top on HN. Slow news day I guess...
Re: Writing a Service Worker
#24What borders me, is that you need an valid SSL cert for an service worker, however there is a develop/test cert here: https://github.com/Eun/test.bi
Re: Writing a Service Worker
#25I always get all stoked on service workers until I remember that half my users are on safari. Then I get bummed.
What's the difference with Safari? (not a JS dev, so this is not familiar territory)
Not implemented. "Under consideration".
Re: Writing a Service Worker
#2620 lines of JS top on HN. Slow news day I guess...
[deleted]
Re: Writing a Service Worker
#27I always get all stoked on service workers until I remember that half my users are on safari. Then I get bummed.
I wouldn't let that stop you: adding a service work won't in any way degrade the experience of Safari users. When used for caching, it's pure progressive enhancement.
Sure, some browsers will have a more robust experience in adverse network conditions, but the experience once a page has loaded will be identical. It's also difficult to accidentally make the worker a hard dependency of a site, since even supported browsers will load the site without the worker on first visit.
Re: Writing a Service Worker
#28I was going to say, "Isn't this what the application cache is for?" then I looked and saw it has been removed from the standards.
Re: Writing a Service Worker
#29How large can the cache get at max?
It's browser specific. Most use a heuristic along the lines of allowing browser storage (inclusive of IndexedDB, etc.) to use a combined 50% of the device's otherwise free space. Usually each origin is limited to around 20% of that potential usage.
Re: Writing a Service Worker
#30Best use case of this I guess, is some kind of flight mode for web apps. Before going in to metro or flight, you click a button, and for example HN caches front page for you.
Caching cross-origin resources is problematic because you can't check the response code: https://stackoverflow.com/q/35626269
You can still cache the response you just don't get to see what the response was. For those types of resources it's best to only fallback to using them if the user is offline.