Russell: CPU Gains Can't Keep Up With Frontend Resource Assumptions
Alex Russell's notes on mobile performance zero in on a gap that frontend engineers tend to overlook: CPUs are not improving quickly enough to absorb the resource assumptions baked into modern client-side builds. 
There is a genuinely bright spot in tooling. Several popular frameworks now ship options for skipping first-party JavaScript entirely — Next.js and Gatsby among them — even though, as Russell puts it, the JS community remains in stubborn denial about what client-side script actually costs. His hope is that these toolchain advances can serve as an accessible bridge toward a reduced-script-emissions world.
Why the View From America Isn't Enough
Much of the performance writing out there is framed around the US. What stands out in Russell's take is that it widens the lens to countries like India. That framing makes the 5G question worth asking: what does the network rollout actually change for developers around the world? The answer calls for skepticism.
5G looks set to continue a bumpy rollout for the next half-decade. Carriers make different frequency band choices in different geographies, and 5G performance is heavily sensitive to mast density, which will add confusion for years to come. Suffice to say, 5G isn't here yet, even if wealthy users in a few geographies come to think of it as "normal" far ahead of worldwide deployment
The practical takeaway is a simple check on assumptions: the way I'm viewing my own site is most likely not the way many other people are viewing it. 



