News for hackers. Stuff that matters.
Re:When to use web workers by whereareyouwow on Saturday June 15, 2019 @01:33PM (#20191058)
Yes @dassurma. But web workers are not everything. Your own blog post does not score 100 : https://developers.google.com/speed/pagespeed/insights/?url=... And those issues are not necessarily addressed with web workers. Good basic static design matters too.
Re:When to use web workers by dassurma on Saturday June 15, 2019 @01:45PM (#20191118)
I never claimed that Web Workers are the silver bullet that will absolve us from all our problems. On the contrary, I don’t think such a silver bullet will ever exist.

I am saying that we should be using web workers to keep the main thread free. That is completely orthogonal to good static design, proper bundling, right caching headers, code splitting, asset hashing etc etc.

Re:When to use web workers by whereareyouwow on Saturday June 15, 2019 @02:00PM (#20191227)
I agree with you on keeping the main thread free. What are your thoughts on WASM via workers?
Re:When to use web workers by dassurma on Saturday June 15, 2019 @02:10PM (#20191272)
We are using loads of Wasm in Workers in https://squoosh.app

Since Wasm is synchronous, I’d say it should almost always be run in workers except if the module needs access to some main-thread-only API.

Re:When to use web workers by true_religion on Saturday June 15, 2019 @04:24PM (#20191914)
They scored a 96. There is exactly one issue, and it’s esoteric in my opinion.