Posts, links, and the occasional book review.
Latest data put out by the telecom regulator pegs the average monthly wireless data usage per user at 10.37 GB, which analysts say could rise by around 15% in the next two quarters if people continue to work from their homes over a prolonged period.
Was going to build this myself, but turns out I don't have to!
A handy suite of tests (from Mark Nottingham) to see how different browsers respond to various caching headers.
Stumbled on this gem reading Jeremy's 2019 recap and what a breath of fresh air.
A collection of good news, positive trends, uplifting statistics and facts — all beautifully visualized by Information is Beautiful.
A rather clever way of looking at performance data by breaking it down into histogram "regions".
Fantastic post detailing Shopify's work optimizing their admin pages. There are some good pointers around profiling and optimizing React, as well as a lot of thoughtful insights on designing in-between states.
Ethan, eloquent as always, on the inaccessibly of AMP Stories:
Conjecture aside, here’s what I do know: the AMP team decided that each of these Story demos was worth showcasing on the official page for AMP Stories. And that sends a powerful signal about where the priorities for AMP Story sit. The content in each AMP Story is wonderful, the visual designs are effective—but if you use a screen reader, each Story is an assault on your senses. And by showcasing these demos, the AMP team is signaling that’s entirely acceptable.
It reminds me of Surma's comments about JS frameworks and performance:
Unless a globally launched framework labels itself as exclusively targeting the users of the Wealthy Western Web, it has a responsibility to help developers target every phone on The Widening Performance Gap™️ spectrum.
It's a big responsibility, but if you're shipping something that will be this widely used, you've got a responsibility to make the default state as secure, accessible and performant as possible.
That's particularly true for something that makes as bold a claim, as aggressively, as AMP has always done.
Remy building on someone else's (smart!) post about lazy-loading YouTube embeds.
Gosh I miss when this "someone blogs and then someone else iterates on that on their own blog" thing was more common.