from Hacker News

Chrome 40 beta: Offline service workers

by aarkay on 12/4/14, 6:28 PM with 12 comments

• by lxgr on 12/4/14, 8:08 PM

  >[...] could do their work even after the page is closed, provided the user has given permission.

  I'm really glad for the second half of that statement.

  While I could imagine a few use cases, the last thing I want on my smartphone are arbitrary bloated sites draining my battery after closing them. I even consider it a feature of websites vs. native apps.

• by msoad on 12/4/14, 7:24 PM

  Service Workers are what Application Cache should have been first. Application Cache has a big flaw and that is, you can't control it much. You depend on browser to decide what to do when there is no Internet connection. With Service Workers you get to programmatically tell browser what to do with network requests and so on.

  Classic configuration file vs. let me write actual code approach. I'm glad we have both now! Application Cache makes sense for a lot of static websites.

• by ropiku on 12/4/14, 8:00 PM

  I'm glad it's a native feature.

  I attended a talk by an FT engineer and I was amazed by what's possible.

  Update: Mistakenly thought that FT uses Polyfill for service workers.