[threeseed]

I hope not as Service Workers is an awful technology.

It is completely hostile to users. If I close a web page I expect everything related to that web page to stop. Immediately. I don't expect there to be lingering background threads consuming battery life, network data and disk storage. And in Chrome you can only discover service workers by enabling a Debug mode and memorising a specific URL. Exactly how does a non-developer figure out what is going on ?

If Apple had any sense they would ban service workers and instead propose use case specific, tightly focused and managed APIs that focus on security and battery life first.

Also just a hint at a future where Botnets are running in your browser:

https://sakurity.com/blog/2016/12/10/serviceworker_botnet.ht...

[EGreg]

Service workers were designed to only work during events which you opted into. Either because you loaded the site which is now making requests, or because you OPTED IN to receive notifications.

Think about it this way... why do you have to download an entire app just to use a site? Don't like the notifications? Turn the off.

[threeseed]

Yes because ordinary users never, ever opt in to things they shouldn't. And because of that one opt-in mistake suddenly they have invisible service workers mining Bitcoins which they could never learn about since the discovery mechanism for service workers is currently non-existent.

Again, the concept of background tasks isn't necessarily a bad thing. But it needs to be locked down to specific use cases not a free for all allowing arbitrary JS to be executed.

[MichaelGG]

So limit the amount of CPU/bw/etc. they can use, just like mobile platforms do for background apps?

[ghughes]

Installing an app is a higher bar than tapping the "get out of my way" button on a modal dialog that some website just shoved in your face.

[MBCook]

Oh good. It can only burn 10% of my battery and bandwidth to make someone else rich. That's fair.