News for hackers. Stuff that matters.
Re:When to use web workers by stefan_ on Saturday June 15, 2019 @04:45PM (#20192039)
I suggest you look up why they disabled it. And that is still not an application of WebWorkers!

It would be much more helpful to the cause if you could point to some actually used app out there principally relying on WebWorkers. Until then, it's been a lot of pain, zero gain.

Re:When to use web workers by Jack000 on Saturday June 15, 2019 @08:03PM (#20192976)
a bit niche, but here's one of my projects - svgnest.com

in addition to the render blocking issue brought up by this article, there are a lot of applications for cpu-bound web apps (eg. anything requiring machine learning or computer vision), but in my experience web workers are not very reliable for this purpose.

Re:When to use web workers by infinite8s on Sunday June 16, 2019 @05:42PM (#20198079)
I use webworkers to run an in-memory streaming pivoting engine (compiled from C++ to wasm) to build real-time Tableau-like dashboards that run fully in the browser (which runs fairly well for 10M row datasets or less). Network IO and the compute is handled in the webworker, which allows the main UI thread to remain responsive.