Re: [whatwg] ServiceWorker bottle-neck design flaw - MS Edge to the rescue?

EDIT 1 Ok, it might have been Safari/Webkit but reading this it looks like 1 process for all ServiceWorker threads plus another to monitor/start/stop, but only one simultaneous SW instance per domain (plus that dodgy iFrame logic webkit has

[whatwg] ServiceWorker bottle-neck design flaw - MS Edge to the rescue?

As you may be aware, I have been lobbying strongly here , and here