On Thu, Oct 19, 2023 at 5:20 AM Kenji Baheux <[email protected]>
wrote:

> Compelling use cases (e.g. actual & reasonably popular products that work
> better or only work when sharedworker are available *on mobile*) would
> help boost the priority over other interop requests.
>

There were enough use cases for Apple to reintroduce shared worker after
removing it.  Classic one is any kind of site where a user may plausibly
have multiple tabs open and need them to remain in sync with the server.
You treat the SharedWorker as the source of truth in terms of talking to
the server, data updates, etc.  So email clients, shared document editors,
etc fit this bill.  Yes, you can accomplish the same thing more awkwardly
other ways with leader-election algorithms using BroadcastChannel or force
ServiceWorker into a SharedWorker model by forcing it to stay alive.  But
forcing sub-optimal solutions is a tax on the web ecosystem for these use
cases and pushes people to build native apps for mobile instead of the web.

I'll also just say I find the framing of "mobile web" as a separate
platform from the web in general or desktop web somewhat surprising and
disappointing.  We should not be bifurcating the web ecosystem without a
good reason.   What is the reason SharedWorker should be desktop-only when
every other browser is able to ship it on mobile?




>
> On Wed, Oct 18, 2023 at 11:04 PM Ben Kelly <[email protected]>
> wrote:
>
>> FWIW, chrome on android is the last holdout on shared workers.  Safari on
>> ios supports it.  It would be nice if this could be prioritized.
>>
>> On Wed, Oct 18, 2023 at 9:44 AM Rik Cabanier <[email protected]> wrote:
>>
>>> One of our users reported that sharedworkers weren't working in the
>>> browser.
>>> After investigating it looks like they were never supported on Android
>>> but it seems that they are supported everywhere else, including mobile
>>> Safari.
>>> Reading
>>> https://monorail-prod.appspot.com/p/chromium/issues/detail?id=154571,
>>> it seems there was a concern that too many sharedworkers would exhaust
>>> system resources. Is that still a concern 10 years later?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "blink-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/34528104-dca4-4a21-b376-013bd393dfc1n%40chromium.org
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/34528104-dca4-4a21-b376-013bd393dfc1n%40chromium.org?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK7rkMjH%2BV42hygYZTH6f9CBj4nfkk4W4rQuaXY84d-r%2BX%3DOmg%40mail.gmail.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK7rkMjH%2BV42hygYZTH6f9CBj4nfkk4W4rQuaXY84d-r%2BX%3DOmg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK7rkMh7dd2t0sRett4h596_95fHp1%3DEwPRXfN74VNfxDYLtQg%40mail.gmail.com.

Reply via email to