Web Workers API

Re:Web Workers API by KubikPixel on Friday December 03, 2021 @03:48AM (#29427960)

Web Workers makes it possible to run a script operation in a background thread separate from the main execution thread of a web application. The advantage of this is that laborious processing can be performed in a separate thread, allowing the main (usually the UI) thread to run without being blocked/slowed down.

[ Parent | on HN ]

Re:Web Workers API by andybak on Saturday December 04, 2021 @08:19AM (#29440648)

Any context? Is there a specific reason to post this now? Web workers aren't new to Firefox, are they?

[ Parent | on HN ]

Re:Web Workers API by k__ on Saturday December 04, 2021 @08:24AM (#29440678)

There was a discussion in another thread about Apple stifling PWAs on iOS.

One point was, web workers aren't supported correctly.

[ Parent | on HN ]

Re:Web Workers API by SahAssar on Saturday December 04, 2021 @09:37AM (#29441069)

IIRC normal workers are supported (dedicated workers) but shared workers are not. Service workers are "supported" but some features that are pretty critical (like push notifications) are not.

[ Parent | on HN ]

Re:Web Workers API by styfle on Saturday December 04, 2021 @09:51AM (#29441163)

I believe this is the other thread: https://news.ycombinator.com/item?id=29440457

[ Parent | on HN ]

Re:Web Workers API by rubyskills on Saturday December 04, 2021 @09:57AM (#29441203)

Also I think push notifications are not supported.

[ Parent | on HN ]

Re:Web Workers API by kitsunesoba on Saturday December 04, 2021 @05:02PM (#29444697)

That can be a great feature in some circumstances, but it also seems like it can undo much of the efficiency improvement browsers have accomplished by throttling and sleeping less used tabs. Do browsers implement any kind of leashing in terms of how much resources any particular site’s workers can use, frequency of running, length of runs, etc?

[ Parent | on HN ]