3 ms·
SharedWorker was implemented in Safari years after Chrome/Firefox I'm sure there are many such examples.
by saxenaabhi 1y ago
SharedWorker was implemented in Safari years after Chrome/Firefox
I'm sure there are many such examples.
- troupo 1y agoShared Workers is weird. Safari released them in 2010, one month after Chrome. And then... removed them in 2013. Firefox implemented them in 2014, Edge in 2020, and Safari re-introduced them in 2022. The was a proposal to remove the spec entirely in 2015: https://github.com/whatwg/html/issues/315 https://github.com/whatwg/html/issues/315 I don't think I've seen a feature that was shipped in s browser for years, then removed, and then shipped again. I'd love to know why. They only explanations I've seen seem to be this: https://x.com/xeenon/status/652573047623323648 https://x.com/xeenon/status/652573047623323648 "The implementation of Shared Web Workers was imposing undesirable constraints on the engine. It never gained any adoption." and this: https://bugs.webkit.org/show_bug.cgi?id=149850#c5 https://bugs.webkit.org/show_bug.cgi?id=149850#c5 "This feature was originally removed temporarily during multiprocess bring-up, and actual usage on the web has been pretty low. We're willing to reconsider if there is significant demand."
- saxenaabhi 1y agoMaybe I'm misremembering but i reckon something about shared memory vulnerabilities.