4 ms·
Yes @dassurma. But web workers are not everything. Your own blog post does not score 100 : https://developers.google.com/speed/pagespeed/insights/?url=https%3
by whereareyouwow 7y ago
Yes @dassurma. But web workers are not everything.
Your own blog post does not score 100 : https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fdassur.ma%2Fthings%2Fwhen-workers%2F&tab=desktop https://developers.google.com/speed/pagespeed/insights/?url=...
And those issues are not necessarily addressed with web workers. Good basic static design matters too.
- dassurma 7y agoI 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.
- whereareyouwow 7y agoI agree with you on keeping the main thread free. What are your thoughts on WASM via workers?
- dassurma 7y agoWe are using loads of Wasm in Workers in https://squoosh.app 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.
- true_religion 7y agoThey scored a 96. There is exactly one issue, and it’s esoteric in my opinion.