You might not need… a service worker
Summary
This post argues that service workers are not always necessary, examining real-world use cases and caching strategies. It emphasizes simpler alternatives like HTTP caching and content hashing, and suggests keeping static assets around to avoid unnecessary invalidations, with a nuanced view of when offline or background capabilities are truly needed.