Static _is_ better for a good bunch of performance metrics. But what about interactive content like https://proxx.app?

The article is mostly aimed at use-cases where some sort of logic in JavaScript is required.

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.

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.

I agree with you on keeping the main thread free. What are your thoughts on WASM via workers?

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.

They scored a 96. There is exactly one issue, and it’s esoteric in my opinion.

Heavily interactive content in the browser is an edge case for vast majority of mobile users.

Outside of that edge case the best solution is usually to use JS to sprinkle functionality not doing heavy lifting.

Within that edge case, an app (possibly using react native, if you love js) is often a better choice.