Surma's longstanding argument that Web Workers are the route to better-feeling sites got another airing in "The State Of Web Workers In 2021." The core observation: other platforms treat parallelism as a baseline expectation rather than an add-on. iOS gives developers Grand Central Dispatch, Android offers the unified task scheduler WorkManager, and game engines such as Unity ship job systems. Those platforms support multithreading — and work to make it easy — for one consistent reason: keeping apps feeling great.
The web has its own equivalent. Because JavaScript itself is single-threaded, developers have to work around that constraint by using Web Workers, which Surma notes are universally supported. The open questions are how to use them and what to put in them.
Moving state and logic into a worker
On the "what," the article demonstrates a game in which the entire app state and game logic run inside a worker. On the "how," the comlink helper library appears to remove a substantial amount of the manual plumbing. But the underlying point is the one quoted from the source piece: parallelism is worth the effort only insofar as it helps the application feel good.
Ensure your app feels great.
Should the tooling take over?
Developer advocacy alone, in CSS-Tricks' view, hasn't moved the needle much. The wish is for mainstream tooling to handle off-main-thread work automatically — for example, Apollo, which manages a large share of app state, transparently doing that work away from the main thread. Whether such an approach makes sense, and whether it is feasible, remains unresolved.



