Alex Russell

  1. The Performance Inequality Gap, 2026

    The Budget, 2026 Edition Let's cut to the chase, shall we? Updated network test parameters for 2026 are: 9 Mbps downlink 3 mbps uplink 100 millisecond RTT Regarding devices, my updated recommendations are the Samsung Galaxy A24 4G (or equivalent) and the HP 14. The goal of these recommendations is to…

    Published

  2. The App Store Was Always Authoritarian

    Eric Prouzet And now we see it clear, like a Cupertino sunrise bathing Mt. Bielawski in amber: Apple will censor its App Store at the behest of the Trump administration without putting up a fight. It will twist words into their antipodes to serve the powerful at the expense of the weak. To better serve…

    Published

  3. 11ty Hacks for Fun and Performance

    This blog really isn't just for beating up on Apple for the way it harms users, the web, standards, and society to maintain power and profits. So here's some fun stuff I've been doing in my 11ty setup to improve page performance. ContentsPage-Specific Resources via Shortcodes and the 11ty BundlerMo Pagination…

    Published

  4. Apple's Antitrust Playbook

    ContentsLies by Any Other NameGreat Artists StealDear Tech Reporters: Access Is Not A Beat This blog is failing on several levels. First, September 2025 is putting the “frequent” in “infrequently”, much to my chagrin. Second, my professional mission is to make a web that's better for everyone, not to…

    Published

  5. Comforting Myths

    Update: The charts below were inappropriately snapped, compressing the range of values. This has been corrected. Feature availability numbers also changed since drafting and are updated. In several recent posts, I've attempted to address how the structure of standards bodies, and their adjacent incubation…

    Published

  6. Web Standards and the Fall of the House of Iamus

    Photo by Photo by Artan Sadiku Commentary about browsers and the features they support is sometimes pejorative towards pre-standardisation features. Given Apple's constriction of Mozilla's revenue stream and its own strategic under-funding of WebKit, this usually takes the form "Chromium just ships whatever…

    Published

  7. Apple's Assault on Standards

    TL;DR: Market competition underlies the enterprise of standards. It creates the only functional test of designs and lets standards-based ecosystems route around single-vendor damage. Without competition, standards bodies have no purpose, and neither they, nor the ecosystems they support, can retain relevance…

    Published

  8. Apple vs. Facebook is Kayfabe

    Photo by Claudia Raya Apple vs. Facebook is, and always was, kayfabe. In reality, Apple is Facebook's chauffeur; holding Zuck's coat while Facebook1 wantonly surveils iPhones owners.2 Facebook's gross profit over time. Facebook and Apple mugged convincingly for the cameras as "App Tracking Transparency…

    Published

  9. Put Names and Dates On Documents

    Anyone who has worked closely with me, or followed on social media [, ], will have seen a post or comment to the effect of: Names and dates on docs. Every time. Don't forget. This is most often tacked onto design documents lacking inline attribution, and is phrased provocatively to make it sticky.…

    Published

  10. How Do Committees Fail To Invent?

    Mel Conway's seminal paper "How Do Committees Invent?" (PDF) is commonly paraphrased as Conway's Law: Organizations which design systems are (broadly) constrained to produce designs which are copies of the communication structures of these organizations. This is deep organisational insight that engineering…

    Published

  11. Links? Links!

    Frances has urged me for years to collect resources for folks getting into performance and platform-oriented web development. The effort has always seemed daunting, but the lack of such a list came up again at work, prompting me to take on the side-quest amidst a different performance yak-shave. If that…

    Published

  12. Conferences, Clarity, and Smokescreens

    Before saying anything else, I'd like to thank the organisers of JSNation for inviting me to speak in Amsterdam. I particularly appreciate the folks who were brave enough to disagree at the Q&A sessions afterwards. Engaged debate about problems we can see and evidence we can measure makes our work better…

    Published

  13. Safari at WWDC '25: The Ghost of Christmas Past

    At Apple's annual developer marketing conference, the Safari team announced a sizeable set of features that will be available in a few months. Substantially all of them are already shipped in leading-edge browsers. Here's the list, prefixed by the year that these features shipped to stable in Chromium…

    Published

  14. If Not React, Then What?

    Over the past decade, my work has centred on partnering with teams to build ambitious products for the web across both desktop and mobile. This has provided a ring-side seat to a sweeping variety of teams, products, and technology stacks across more than 100 engagements. While I'd like to be spending…

    Published

  15. Platform Strategy and Its Discontents

    This post is an edited and expanded version of a now-mangled Mastodon thread. ContentsPlatforms Are Competitions...and We're LosingWin ConditionYou Do It To Yourself, And That's What Really HurtsGroundhog DayReboot Some in the JavaScript community imagine that I harbour an irrational dislike of their…

    Published

  16. Reckoning: Part 4 — The Way Out

    Other posts in the series: Reckoning: Part 1 — The Landscape Reckoning: Part 2 — Object Lesson Reckoning: Part 3 — Caprock Frontend took ill with a bad case of JavaScript fever at the worst possible moment. The predictable consequence is a web that feels terrible most of the time, resulting in low and…

    Published

  17. Reckoning: Part 3 — Caprock

    Other posts in the series: Reckoning: Part 1 — The Landscape Reckoning: Part 2 — Object Lesson Reckoning: Part 4 — The Way Out ContentsComplexity PerplexityCarrying CapacityShould This Be An SPA?The PitsAftermath Last time, we looked at how JavaScript-based web development compounded serving errors on…

    Published

  18. Reckoning: Part 2 — Object Lesson

    Other posts in the series: Reckoning: Part 1 — The Landscape Reckoning: Part 3 — Caprock Reckoning: Part 4 — The Way Out --> ContentsThe Golden WaitThe Truth Is In The TraceZip ItNear PeersBlimeyJavaScript MasshatteryMaryland Enters The ChatChattanooga Chug ChugSNAP? In Jersey? FuhgeddabouditHoosier…

    Published

  19. Reckoning: Part 1 — The Landscape

    Instead of an omnibus mega-post, this investigation into JavaScript-first frontend culture and how it broke US public services has been released in four parts. Other posts in the series: Reckoning: Part 2 — Object Lesson Reckoning: Part 3 — Caprock Reckoning: Part 4 — The Way Out When you live in the…

    Published

  20. Misfire

    The W3C Technical Architecture Group1 is out with a blog post and an updated Finding regarding Google's recent announcement that it will not be imminently removing third-party cookies. The current TAG members are competent technologists who have a long history of nuanced advice that looks past the shouting…

    Published

  21. Why Browsers Get Built

    There are only two-and-a-half reasons to build a browser, and they couldn't be more different in intent and outcome, even when they look superficially similar. Learning to tell the difference is helpful for browser project managers and engineers, but also working web developers who struggle to develop…

    Published

  22. Home Screen Advantage

    Update: OWA is out with an open letter appealing to Apple to do better. If you care about the future of the web, I encourage you to sign it, particularly if you live in the EU or build products for the common market. After weeks of confusion and chaos, Apple's plan to kneecap the web has crept into view…

    Published

  23. The Performance Inequality Gap, 2024

    The global device and network situation continues to evolve, and this series is an effort to provide an an up-to-date understanding for working web developers. So what's changed since last year? And how much HTML, CSS, and (particularly) JavaScript can a new project afford? ContentsThe Budget, 2024JavaScript…

    Published

  24. Why Are Tech Reporters Sleeping On The Biggest App Store Story?

    The tech news is chockablock1 with antitrust rumblings and slow-motion happenings. Eagle-eyed press coverage, regulatory reports, and legal discovery have comprehensively documented the shady dealings of Apple and Google's app stores. Pressure for change has built to an unsustainable level. Something's…

    Published

  25. Safari 16.4 Is An Admission

    If you're a web developer not living under a rock, you probably saw last week's big Safari 16.4 reveal. There's much to cheer, but we need to talk about why this mega-release is happening now, and what it means for the future. ContentsWebKit's Roaring TwentiesGood Things Come In SixesWhat Changed?Headcount…

    Published

  26. The Market for Lemons

    For most of the past decade, I have spent a considerable fraction of my professional life consulting with teams building on the web. It is not going well. Not only are new services being built to a self-defeatingly low UX and performance standard, existing experiences are pervasively re-developed on…

    Published

  27. The Performance Inequality Gap, 2023

    TL;DR: To serve users at the 75th percentile (P75) of devices and networks, we can now afford ~150KiB of HTML/CSS/fonts and ~300-350KiB of JavaScript (gzipped). This is a slight improvement on last year's budgets, thanks to device and network improvements. Meanwhile, sites continue to send more script…

    Published

  28. Apple Is Not Defending Browser Engine Choice

    Gentle reader, I made a terrible mistake. Yes, that's right: I read the comments on a MacRumors article. At my age, one knows better. And yet. As penance for this error, and for being short with Miguel, I must deconstruct the ways Apple has undermined browser engine diversity. Contrary to claims of Apple…

    Published

  29. A Management Maturity Model for Performance

    Since 2015 I have been lucky to collaborate with more than a hundred teams building PWAs and consult on some of the world's largest sites. Engineers and managers on these teams universally want to deliver great experiences and have many questions about how to approach common challenges. Thankfully, much…

    Published

  30. Cache and Prizes

    If you work on a browser, you will often hear remarks like, Why don't you just put [popular framework] in the browser? This is a good question — or at least it illuminates how browser teams think about tradeoffs. Spoiler: it's gnarly. Before we get into it, let's make the subtext of the proposal explicit…

    Published