# Alex Russell

Alex Russell on browsers, standards, and the process of progress.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Corruption Is A Cost-of-Living Issue: App Store Edition

DevFeed: [Corruption Is A Cost-of-Living Issue: App Store Edition](<https://devfeed.tech/articles/corruption-is-a-cost-of-living-issue-app-store-edition-123506.md>)

Original publisher: [Read original article](<https://infrequently.org/2026/11/app-stores-pwas-and-corruption/>)

Author: Alex Russell

Published: 2026-11-08T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [appstores](<https://devfeed.tech/topics/appstores.md>), [vendor lock-in](<https://devfeed.tech/topics/vendor-lock-in.md>), [trust and safety](<https://devfeed.tech/topics/trust-and-safety.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [app-store](<https://devfeed.tech/tags/app-store.md>), [app-stores](<https://devfeed.tech/tags/app-stores.md>), [apps](<https://devfeed.tech/tags/apps.md>), [blog](<https://devfeed.tech/tags/blog.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [competition](<https://devfeed.tech/tags/competition.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [control](<https://devfeed.tech/tags/control.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [democracy](<https://devfeed.tech/tags/democracy.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [fees](<https://devfeed.tech/tags/fees.md>), [gatekeepers](<https://devfeed.tech/tags/gatekeepers.md>), [ice](<https://devfeed.tech/tags/ice.md>), [malware](<https://devfeed.tech/tags/malware.md>), [politics](<https://devfeed.tech/tags/politics.md>), [store](<https://devfeed.tech/tags/store.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The author argues that Apple and Google's app store monopolies are linked to both political corruption and higher costs, while their security claims mask weak platform protections and concentrated control. The text says malware protection depends mainly on operating system and browser boundaries, not store reviews or distribution contracts. It traces how mobile app store control restricted competition, raised switching costs and passed fees to consumers, while limiting the web's role as an open counterbalance. It calls for mandated interoperability, with stronger browser competition described as the quickest, least risky step, and points to the EU Digital Markets Act as evidence that Apple can be compelled to offer some interoperability without leaving the market. The excerpt argues that congressional investigations should examine these market structures as well as app store conduct tied to ICE.

### Source excerpt

While I'm not shy about my pro-democracy, anti-authoritarian politics, this blog has kept to a more technical lane, veering into policy only out of necessity. As the scale of the web's setbacks at the hands of proprietary forces became clear, it became urgent to explain the forces at work and raise the alarm. But politics are inescapable now; the abuses inherent in centralised control of native app platforms aren't just enabling violent repression on foreign shores, but threaten the democracy I call home. Not coincidentally, the same forces have driven up prices for consumers and businesses. The control demanded by app stores has served to excuse insufficient platform security while concentrating wealth to a shocking degree, warping public policy along the way. The moral outrages of ICE are just the latest in a long line of corruptions the app stores have fathered. App stores exist to protect gatekeepers, not users, but we abide them specifically because they claim to make us safer. That center cannot hold. The cursory reviews that app stores apply are no substitute for platform security. Protection against malware depends on boundaries enforced by OSes and browsers, not distribution contracts or pre-publication scans, rendering the justifications for the concentration of power by duopolists moot.1 App stores have used the patina of security to pull off the greatest coup of chokepoint capitalism in history, raising prices for every service and and funnelling wealth upward in a spiral of omni-corruption. From embedded distribution fees, to restricted competition, higher switching costs, and transaction taxes passed on to consumers, "native apps" have fleeced the American people for nearly twenty years. And now that unaccountable power has caved to authoritarians. It was only a matter of time before the tools of elite capitulation were weaponised against civil society. The shock of the stores enabling ICE and the abuse of women creates space for moral clarity. We can

## Customizing Eleventy Syntax Highlighting with Line Numbers and MicroLighter

DevFeed: [Customizing Eleventy Syntax Highlighting with Line Numbers and MicroLighter](<https://devfeed.tech/articles/from-prismjs-to-better-prismjs-to-microlighter-in-three-painless-steps-55718.md>)

Original publisher: [Read original article](<https://infrequently.org/2026/09/microlighter/>)

Author: Alex Russell

Published: 2026-09-20T00:00:00Z

Content type: article

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Eleventy](<https://devfeed.tech/topics/eleventy.md>), [Highlight.js](<https://devfeed.tech/topics/highlightjs.md>), [Syntax Highlighting](<https://devfeed.tech/topics/syntax-highlighting.md>), [MkDocs](<https://devfeed.tech/topics/mkdocs.md>), [CSS](<https://devfeed.tech/topics/css.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Nunjucks](<https://devfeed.tech/topics/nunjucks.md>)

Tags: [11ty](<https://devfeed.tech/tags/11ty.md>), [css](<https://devfeed.tech/tags/css.md>), [eleventy](<https://devfeed.tech/tags/eleventy.md>), [js](<https://devfeed.tech/tags/js.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [syntax-highlighting](<https://devfeed.tech/tags/syntax-highlighting.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

An Eleventy-focused article compares PrismJS syntax highlighting with a custom shortcode approach for adding line numbers and considers MicroLighter as an alternative for improved markup and highlighting behavior.

### Source excerpt

An excellent feature of Eleventy1 is the official PrismJS-based syntax highlighting plugin, which adds painless build-time syntax highlighting. It keeps 11ty sites from worrying about client-side bloat from JS-based highlighters and the common failure mode of over-including language definitions.2 But nothing's perfect. Contents Lilliputian Adventures In Line Numbering Greener Pastures The official plugin integrates naturally, and I took to using it via the usual triple-backtick markdown syntax: # The Usual Markdown Nonsense { #the-usual-nonsense } And now for something entirely different: ```js function yourCodeHere() { /* ... */ } ``` Etc., etc. This works a treat, until you want a bit more control. At that point, what seems magical starts to feel restrictive. Lilliputian Adventures In Line Numbering A recent goal was to add line numbers. After reading some of the plugin code that invokes PrismJS, I closed my laptop in frustration, unable to cajole eleventy-plugin-syntaxhighlight into outputting line numbers. Walking away from the keyboard paid off a few days later when I recalled the paired shortcode code path generated stable per-line delimiters. This allowed reuse of the plugin's primary logic, wrapped in a bit of string munging to add the necessary styling hooks: // From this site's Eleventy config file // Because my esm conversion is still partial: const { default: syntaxHighlight } = await import("@11ty/eleventy-plugin-syntaxhighlight"); // ... module.exports = async function(config) { // ... let syntaxHighlightOptions = { // For faster CSS selectors preAttributes: { highlighted: "highlighted" }, codeAttributes: { highlighted: "highlighted" }, }; config.addPlugin(syntaxHighlight, syntaxHighlightOptions); config.addPairedShortcode("code", function(content, language="", highlightLines="") { // The design of cssMin and addToBundle are outside // the scope of this post. // // Suffice to say, we're inlining the contents // of the file path passed as an argument to

## Why Code Removal May Be Preferable to Scheduling for Performance Remediation

DevFeed: [Why Code Removal May Be Preferable to Scheduling for Performance Remediation](<https://devfeed.tech/articles/the-wicked-reason-removing-code-beats-better-scheduling-26567.md>)

Original publisher: [Read original article](<https://infrequently.org/2026/08/notes-on-performance-remediation-strategies/>)

Author: Alex Russell

Published: 2026-08-19T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Code](<https://devfeed.tech/topics/code.md>), [ordering](<https://devfeed.tech/topics/ordering.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [ordering](<https://devfeed.tech/tags/ordering.md>), [performance](<https://devfeed.tech/tags/performance.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

An opinion article arguing that removing code can be a more reliable performance-remediation strategy than reordering or deferring work. It says both approaches require understanding page behavior, while scheduling changes can increase validation, coordination, bandwidth, and main-thread performance risks.

### Source excerpt

My colleague Marko Ilić has published an insightful piece on how to schedule work on the critical path, and I recommend reading it before proceeding here. Contents Elimination vs. Scheduling: An Organisational Perspective What's Good for the Goose... "Preloading" as Scheduling Scheduling Is For Closers General-Purpose Advice ...and welcome back. As you likely anticipated, Marko's beautifully presented post kicked off healthy discussions around the office. Since we almost always see eye-to-eye, it seemed interesting to surface some of that discussion here. With his permission, what follows are expanded versions of some points I posed in reply. Elimination vs. Scheduling: An Organisational Perspective There's no daylight between our positions on code reduction: sending and running less is always ideal. Where we differ, perhaps, is the priority teams should assign to scheduling vs. code removal in their performance remediation efforts. Contra Marko, I posit that reordering can almost never be assumed to be cheaper or easier. While it may be hard to remove code, my view is that it is generally not harder than re-ordering in most codebases. Why? The primary cost of both code removal and scheduling interventions is the investment to deeply understand page behaviour. This presents a narrative challenge to the proposition that scheduling is an easier fix, as both approaches share the largest cost. At the team level, the consequences of restructuring are harder to reason about than direct removal, reducing potential upside and increasing validation costs. Bytes that are only deferred still contend for bandwidth, potentially delaying above-the-fold resources in ways that only become visible in the tail of the connection quality curve. Worse, late-fetched JS resources generate heavy "thuds" when residual allocations from background compilation arrive on the main thread. These stalls show up in INP data, but can be maddening to track down due to their stochastic relationship wi

## The Absolute State of Management

DevFeed: [The Absolute State of Management](<https://devfeed.tech/articles/the-absolute-state-of-management-26566.md>)

Original publisher: [Read original article](<https://infrequently.org/2026/07/state-management/>)

Author: Alex Russell

Published: 2026-07-23T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [state-management](<https://devfeed.tech/topics/state-management.md>), [React](<https://devfeed.tech/topics/react.md>), [Zustand](<https://devfeed.tech/topics/zustand.md>), [apollo-client](<https://devfeed.tech/topics/apollo-client.md>), [Redux](<https://devfeed.tech/topics/redux.md>), [Library](<https://devfeed.tech/topics/library.md>)

Tags: [apollo](<https://devfeed.tech/tags/apollo.md>), [frameworkism](<https://devfeed.tech/tags/frameworkism.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [react](<https://devfeed.tech/tags/react.md>), [redux](<https://devfeed.tech/tags/redux.md>), [state](<https://devfeed.tech/tags/state.md>), [state-management](<https://devfeed.tech/tags/state-management.md>), [tanstack](<https://devfeed.tech/tags/tanstack.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [ui](<https://devfeed.tech/tags/ui.md>), [webdev](<https://devfeed.tech/tags/webdev.md>), [zustand](<https://devfeed.tech/tags/zustand.md>)

### AI overview

The excerpt argues that React and its ecosystem's many "state management" libraries use the same label for different roles. It lists tools including MobX, Recoil, Jotai, XState, Apollo, Redux, TanStack Store, and Zustand, noting that several may appear on one page despite React's own state facilities. The author's central claim is that these tools do not meaningfully manage state: they may encapsulate it, filter or transform updates, and propagate change notifications. The excerpt cuts off before explaining the distinction further.

### Source excerpt

It is by no means the gravest linguistic crime of the React epoch,1 but "state management" grates like nails on chalkboard. A Socratic dialogue I keep having about it goes something like this: me: This UI is far too heavyweight for what it does, have you considered not using React? them: But how will we do state management without React? me: What do you mean? <alternatives> are reactive. them: React manages state in our app. me: It does? Then what are <various_libraries> for? them: Oh, those manage state. me: The libraries that trigger this "Who's on First?" routine include: MobX, which promises "simple, scalable state management." Satchel, apparently, "is characterized by exposing an observable state that makes view updates painless and efficient" Recoil, billed as "a state management library for React" Jotai, which pledges "primitive and flexible state management for React" XState, a "state management and orchestration solution for JavaScript and TypeScript apps" Apollo, promising "a comprehensive GraphQL state management library for JavaScript" Redux, tagline: "a predictable state container for JavaScript apps." TanStack Store, "a framework-agnostic state primitive for immutable updates" Zustand, described as the "🐻 bear necessities for state management in React" Contrasts sharp enough to cut softened butter.2 Suffice it to say, the ecosystem has not picked a winner. Indeed, I regularly see several of these libraries on a single page. But even one would seem too many, given that we're adding a second "state management" system to a framework that spills considerable documentation ink chest-beating about its state management facilities. One of the following must be true: React is a state management system and someone has smuggled in a duplicative dependency we can jettison. React is an inadequate state management system and we should stop trusting it with an ill-defined subset of the "state management" problem. React is not a state management system and we should s

## Abject Praise

DevFeed: [Abject Praise](<https://devfeed.tech/articles/abject-praise-26565.md>)

Original publisher: [Read original article](<https://infrequently.org/2026/07/abject-praise/>)

Author: Alex Russell

Published: 2026-07-06T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Chromium](<https://devfeed.tech/topics/chromium.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [cadence](<https://devfeed.tech/tags/cadence.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [competition](<https://devfeed.tech/tags/competition.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [ios-27](<https://devfeed.tech/tags/ios-27.md>), [openweb](<https://devfeed.tech/tags/openweb.md>), [quality](<https://devfeed.tech/tags/quality.md>), [releases](<https://devfeed.tech/tags/releases.md>), [safari](<https://devfeed.tech/tags/safari.md>), [tests](<https://devfeed.tech/tags/tests.md>), [web](<https://devfeed.tech/tags/web.md>), [web-platform](<https://devfeed.tech/tags/web-platform.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The excerpt argues that Safari's apparent Web Platform Tests gains over Firefox are misleading without accounting for release cadence. Safari added 1,558 passing tests between nightly and stable builds versus Firefox's 990, but its slower release cycle yields about 207 improved tests per week, compared with Firefox's 230 and Chromium's 460. A longer comparison from July 2025 also shows WebKit as the least improved of the three, though the author notes that new browser features continually expand the test baseline. The excerpt frames Safari's quality focus as welcome but questions how much relief its slow pace and fixes for issues competitors largely avoided offer web developers.

### Source excerpt

It's perilous to disagree with someone as wise and thoughtful as Jeremy, but for the past fortnight his post in response to Apple's iOS 27 marketing invades my quiet moments like a cricket in the attic. "Why", I ruminate, "should someone who understands the state of play give Apple credit for doing less than the minimum while rubbishing those who have consistently done more?" Contents Redux Features Over Tests Focus Areas Consequences You Do Not Have To Hand It To Them Everywhere You Turn Quality Has A Quality All Its Own Redux Like Apple's previous marketing of Safari 16.4 and Safari 26, the conjoined September release of Safari and iOS 27 documents an achingly slow release cycle. It would be one thing if the features or spec conformance were world-beating, but looking closely at the release notes, Safari 27 is set to deliver fixes for issues that, by and large, competing engines didn't suffer.1 Don't get me wrong: it's great that Apple is focusing on quality; it remains a persistent issue for Safari. But how much relief should long-suffering web developers expect? The best comparative measures come from the communal Web Platform Tests project. Comparing the current experimental builds with stable channel releases can illuminate the scale of change we can expect when the next major version of each browser launches:2 WPT Test Pass Rates (%) 90% is the minimum Apple requires across all WPT tests for competitors' engines in the EU and Japan where it has been forced to allow them (in theory). Safari barely clears the bar. Source: wpt.fyi It would appear that Safari is closing on Firefox, but this is misleading. Apple managed seven releases over the past year, or a roughly eight week cadence. Mozilla and Chromium, meanwhile, have released 12 versions to stable, or one a month. These serve as denominators (7.4 weeks vs. 4.3) when calculating rates of improvement. Safari's larger increase in passing tests between nightly and stable versions (1558 vs. 990 for Firefox) look

## The Web Is An Antitrust Wedge

DevFeed: [The Web Is An Antitrust Wedge](<https://devfeed.tech/articles/the-web-is-an-antitrust-wedge-26564.md>)

Original publisher: [Read original article](<https://infrequently.org/2026/04/the-web-is-an-antitrust-wedge/>)

Author: Alex Russell

Published: 2026-04-03T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Web](<https://devfeed.tech/topics/web.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [App](<https://devfeed.tech/topics/app.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [apps](<https://devfeed.tech/tags/apps.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [competition](<https://devfeed.tech/tags/competition.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [regulatory](<https://devfeed.tech/tags/regulatory.md>), [web](<https://devfeed.tech/tags/web.md>), [web-apps](<https://devfeed.tech/tags/web-apps.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

This opinion argues that browsers and progressive web apps should be central to antitrust efforts targeting mobile ecosystems. It contends that regulators are accepting weak enforcement and that focusing mainly on alternative native app stores may leave the existing mobile duopoly's power intact.

### Source excerpt

TL;DR: Armed with new powers to rein in the worst excesses of mobile's duopolists, antitrust bodies around the world are struggling to find their footing, and an incurious tech press is letting it pass with nary a nod. Browsers are app stores, but that perspective is almost entirely absent from the antitrust conversation. Instead of prioritising the one, narrow intervention that can safely unlock maximal competition, regulators are gripped by alt store fever dreams; driving down cul-de-sacs that will leave the duopolists' power intact even if new native app stores materialise. Worse, enforcers of new regulations are choking in the face of blatant non-compliance. Laws designed to kickstart competition and unchain web apps are being flouted, but regulators seem unfazed. The web is an engine of interoperability; this was understood by the drafters of these laws, but enforcers have not internalised the lesson, with the UK's CMA being only the latest to pose capitulation as success. Instead of unlocking growth and dynamism, overcautious regulators are ratifying non-compliance through inaction. Timidity today reduces room for manoeuvre tomorrow while hampering home-grown competitors to Big Tech. As it did twenty-five years ago, the web can unlock maximum change with the lowest risk, but regulators are falling down on the job, and tech reporters are not informing readers of the options or the stakes. It's time we spoke plainly about these overlapping institutional failures. Contents Open Societies Necessitate Interoperability Shared Premises Alt Stores, PWAs, and the App Store Endgame Regulators Are Missing The Ripest Opportunity Cupertino is Running Circles Around Brussels, Tokyo, and London Browsers Are App Stores Our Tech Press is Missing the Story, Too It's a day that ends in "y", which means The Verge is at it again: covering the regulatory tussle over mobile ecosystems without mentioning browsers, the web, or PWAs. This long-established pattern is as frustrating as i

## Naked Power

DevFeed: [Naked Power](<https://devfeed.tech/articles/naked-power-26563.md>)

Original publisher: [Read original article](<https://infrequently.org/2026/01/naked-power/>)

Author: Alex Russell

Published: 2026-01-20T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [X (Twitter)](<https://devfeed.tech/topics/twitter.md>), [trust and safety](<https://devfeed.tech/topics/trust-and-safety.md>), [appstores](<https://devfeed.tech/topics/appstores.md>)

Tags: [administration](<https://devfeed.tech/tags/administration.md>), [antitrust](<https://devfeed.tech/tags/antitrust.md>), [app-store](<https://devfeed.tech/tags/app-store.md>), [apple](<https://devfeed.tech/tags/apple.md>), [apps](<https://devfeed.tech/tags/apps.md>), [billionaire](<https://devfeed.tech/tags/billionaire.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [business](<https://devfeed.tech/tags/business.md>), [children](<https://devfeed.tech/tags/children.md>), [competition](<https://devfeed.tech/tags/competition.md>), [control](<https://devfeed.tech/tags/control.md>), [court](<https://devfeed.tech/tags/court.md>), [essential](<https://devfeed.tech/tags/essential.md>), [failure](<https://devfeed.tech/tags/failure.md>), [free](<https://devfeed.tech/tags/free.md>), [google](<https://devfeed.tech/tags/google.md>), [impact](<https://devfeed.tech/tags/impact.md>), [install](<https://devfeed.tech/tags/install.md>), [investigations](<https://devfeed.tech/tags/investigations.md>), [power](<https://devfeed.tech/tags/power.md>), [press](<https://devfeed.tech/tags/press.md>), [principles](<https://devfeed.tech/tags/principles.md>)

### AI overview

The excerpt argues that Apple and Google left Twitter available in their app stores for weeks while Grok-related abuse of women and girls spread, despite their stated policies and Apple's claim that App Store control protects users. It attributes their inaction to concern that confronting Musk could damage short-term business prospects with an administration aligned with him. The author presents the episode as evidence that the companies' safety rationale and principles yield to business and political pressures, and says civil society pressure, regulatory investigations, and bans in multiple continents appeared to prompt Musk to back down to an uncertain degree. The excerpt ends as the author begins to examine the app stores' justifications.

### Source excerpt

Twitter's descent into a gutter of the lowest order has been wrenching: Elon Musk's Grok and the Mass Undressing Scandal As I draft this, a week later, it appears pressure from civil society, investigations by regulators, and outright bans on multiple continents have forced Musk to back down to an uncertain degree. As this scandal roiled, Twitter's apps have been continuously available in Google's Play and Apple's App Store, marking new lows in moral cowardice and non-enforcement of the duopolist's own policies. Now we sit on tenterhooks, wondering if the worst has actually passed. What outrage the will the valley's billionaire man-children unleash next? Meanwhile, we brace for this episode to embolden censorious authoritarians keen to suppress a free press and legitimate speech they dislike. This is the backdrop to Elizabeth Lopatto's must-read denunciation in The Verge: It is genuinely unbelievable to me that I wasted hours of my actual life on a court case where Apple explained it needed total control of its App Store to protect its users. Total control of the App Store was Apple's main argument against antitrust enforcement: The company insisted that its monopolistic control of what users could install on their phones was essential to create a walled garden where it could protect children from unsafe content. Ha! Ha ha ha!! -- Elizabeth Lopatto, "Tim Cook and Sundar Pichai are cowards, The Verge" Failure to react to the "everything app" going all-in on abuse of women and girls for weeks reveals the illegitimacy of their mobile monopolies1; anyone pretending otherwise is a fool or a dupe. We don't need to guess why they sat on their hands. Acting against Musk's abusive apps might put Apple and Google out of favour with an erratic, power-tripping administration which in turn could impact short-term business prospects. Their stated principles are incompatible with maximizing shareholder value under competitive authoritarianism. Recall that both firms lent their mono

## The Performance Inequality Gap, 2026

DevFeed: [The Performance Inequality Gap, 2026](<https://devfeed.tech/articles/the-performance-inequality-gap-2026-26562.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/11/performance-inequality-gap-2026/>)

Author: Alex Russell

Published: 2025-11-24T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Web Development](<https://devfeed.tech/topics/web-development.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [Network](<https://devfeed.tech/topics/network.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [core-web-vitals](<https://devfeed.tech/tags/core-web-vitals.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [devices](<https://devfeed.tech/tags/devices.md>), [doom](<https://devfeed.tech/tags/doom.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [network](<https://devfeed.tech/tags/network.md>), [performance](<https://devfeed.tech/tags/performance.md>), [tls](<https://devfeed.tech/tags/tls.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

This article updates network and device assumptions for 2026 and derives resource budgets for three- and five-second page loads. It argues that growing page sizes and JavaScript payloads worsen performance inequality, while noting that fewer than half of mobile origins pass Core Web Vitals.

### Source excerpt

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 emulate a 75th percentile user experience, meaning a full quarter of devices and networks will perform worse than this baseline. Plugging these parameters into the updated budget calculator, we can derive critical-path resource thresholds for three and five second page load targets. Per usual, we consider pages built in two styles: JS-light, where only 15% of critical-path bytes are JavaScript, and JS-heavy, comprised of 50% JavaScript: Time JS-light (MiB) JS-heavy Total JS Other Total JS Other 3 sec 2.0 0.3 1.7 1.2 0.62 0.62 5 sec 3.7 0.57 3.2 2.3 1.15 1.15 Note: Budgets account for two TLS connections. Many sites initiate more early connections, reducing time available to download resources. Using four connections cuts the three-second budget by 350 KiB, to 1.5 MiB / 935 KiB. The five-second budget loses nearly half a megabyte, dropping to 3.2 / 1.9 MiB. It pays to adopt H/2 or H/3 and consolidate connections. These budgets are extremely generous. Even the target of three seconds is lavish; most sites should be able to put up interactive content much sooner for nearly all users. Meanwhile, sites are ballooning. The median mobile page is now 2.6 MiB, blowing past the size of DOOM (2.48 MiB) in April. The 75th percentile site is now larger than two copies of DOOM. P90+ sites are more than 4.5x larger, and sizes at each point have doubled over the past decade. Put another way, the median mobile page is now 70 times larger than the total storage of the computer that landed men on the moon. Median page weights are more than 2.5x larger for mobile sites than a decade ago, and sites at the 75th percentile are now 4x their 2015 weight. An outsized contributor to this bloat co

## The App Store Was Always Authoritarian

DevFeed: [The App Store Was Always Authoritarian](<https://devfeed.tech/articles/the-app-store-was-always-authoritarian-26561.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/10/the-app-store-was-always-authoritarian/>)

Author: Alex Russell

Published: 2025-10-11T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Web app](<https://devfeed.tech/topics/webapp.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>), [PWA](<https://devfeed.tech/topics/pwa.md>)

Tags: [app-store](<https://devfeed.tech/tags/app-store.md>), [apple](<https://devfeed.tech/tags/apple.md>), [apps](<https://devfeed.tech/tags/apps.md>), [appstores](<https://devfeed.tech/tags/appstores.md>), [browser](<https://devfeed.tech/tags/browser.md>), [competition](<https://devfeed.tech/tags/competition.md>), [developers](<https://devfeed.tech/tags/developers.md>), [dma](<https://devfeed.tech/tags/dma.md>), [eu](<https://devfeed.tech/tags/eu.md>), [government](<https://devfeed.tech/tags/government.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [ios](<https://devfeed.tech/tags/ios.md>), [opensocieties](<https://devfeed.tech/tags/opensocieties.md>), [regulation](<https://devfeed.tech/tags/regulation.md>), [regulators](<https://devfeed.tech/tags/regulators.md>), [right-to-repair](<https://devfeed.tech/tags/right-to-repair.md>), [tariffs](<https://devfeed.tech/tags/tariffs.md>), [trump-administration](<https://devfeed.tech/tags/trump-administration.md>), [us](<https://devfeed.tech/tags/us.md>), [web](<https://devfeed.tech/tags/web.md>), [web-applications](<https://devfeed.tech/tags/web-applications.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The excerpt argues that Apple's App Store control and its resistance to EU Digital Markets Act enforcement are tied to protecting revenue from services and app commissions. It says the DMA could enable safer web interoperability by requiring browser engine choice on iOS, allowing web applications to challenge App Store distribution. The author presents this as a deeper threat to Apple's rent-based model than tariffs, which the excerpt characterizes as mainly affecting near-term costs and upgrades. It also alleges Apple sought government support against regulation while accommodating the Trump administration's censorship demands.

### Source excerpt

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 autocrats, it will talk out both sides of its mouth in ways it had previously reserved for dissembling arguments against threats to profits, like right-to-repair and browser choice. They are, of course, linked. Contents Who's Afraid of the Big Bad Web? Dots Unconnected "Who should rule?" The Price of High Modernism is Dignity Endnote: Let's Talk About Google Apple bent the knee for months, leaving many commentators to ask why. But the reasons are not mysterious: Apple wants things that only the government can provide, things that will defend and extend its power to extract rents, rather than innovate. Namely, selective exemption from tariffs and an end to the spectre of pro-competition regulation that might bring about real browser choice. Over the past few weeks, Tim Apple got a lot what he paid for,1 with the full weight of the US foreign and industrial policy apparatus threatening the EU over DMA enforcement. This has been part of a full-court press from Cupertino. Apple simultaneously threatened the EU while rolling out fresh astroturf for pliant regulators to recline on. This is loud, coordinated, and calculated. But calculated to achieve what? Why is the DMA such a threat to Apple? Interoperability. The DMA holds the power to unlock true, safe, interoperability via the web. Its core terms require that Apple facilitate real browser engine choice, and Apple is all but refusing, playing games to prevent powerful and safe iOS browsers and the powerful web applications they facilitate. Web applications that can challenge the App Store. Unlike tariffs, which present a threat to short-term profits through higher costs and suppression of upgrades in the near term, inter

## 11ty Hacks for Fun and Performance

DevFeed: [11ty Hacks for Fun and Performance](<https://devfeed.tech/articles/11ty-hacks-for-fun-and-performance-26560.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/10/11ty-hacks-for-fun-and-performance/>)

Author: Alex Russell

Published: 2025-10-04T00:00:00Z

Content type: tutorial

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Script](<https://devfeed.tech/topics/script.md>), [Nunjucks](<https://devfeed.tech/topics/nunjucks.md>), [Markdown](<https://devfeed.tech/topics/markdown.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [11ty](<https://devfeed.tech/tags/11ty.md>), [async](<https://devfeed.tech/tags/async.md>), [blog](<https://devfeed.tech/tags/blog.md>), [blogging](<https://devfeed.tech/tags/blogging.md>), [build](<https://devfeed.tech/tags/build.md>), [code](<https://devfeed.tech/tags/code.md>), [fun](<https://devfeed.tech/tags/fun.md>), [hacks](<https://devfeed.tech/tags/hacks.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [js](<https://devfeed.tech/tags/js.md>), [module](<https://devfeed.tech/tags/module.md>), [performance](<https://devfeed.tech/tags/performance.md>), [script](<https://devfeed.tech/tags/script.md>), [web](<https://devfeed.tech/tags/web.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

A developer shares techniques for improving performance in an 11ty site, including selectively loading shortcode resources through the 11ty Bundle plugin, avoiding duplicate scripts, and handling Nunjucks and Markdown preprocessing.

### Source excerpt

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. Contents Page-Specific Resources via Shortcodes and the 11ty Bundler Mo Pagination, Mo Problems Build Time Impact Scroll-Position Based Delayed Code Loading Faster CSS Selectors for 11ty Syntax Highlighting Lean Rada's CSS-only Low-Quality Image Previews Bonus Hack: Global Acronyms for Better Abbreviations Does It Work? Page-Specific Resources via Shortcodes and the 11ty Bundler You know how it gets once you've got a mature 11ty setup: shortcodes proliferate, and some generate output that might depend on JS or CSS. If your setup is anything like mine, you might also feel conflicted about including some of those resources globally. It's important to have them available for the posts that need them, but it's not great to bring a charting library, e.g., into every page when only 1 in 20 will need it. This blog has grown many such shortcodes that generate expansions for features like: Web Components for YouTube and Vimeo embeds WebPageTest.org test embeds plot.js based charts Here, for instance, is how a Vimeo embed looks in the markdown of a page, using Nunjucks for Markdown pre-processing: {% vimeo "VIDEOID", "TITLE" %} This expands to: <lite-vimeo videoid="VIDEOID" videotitle="TITLE"> <a href="http://vimeo.com/VIDEOID">TITLE</a> </lite-vimeo> But this also requires script; e.g.: <script type="module" async src="/assets/js/lite-vimeo/lite-vimeo.js"> </script> And the list keeps growing. To avoid having the weight of these components clogging up every page, a system for selectively pulling in their code would be helpful. It'd also be grand if we could make sure scripts appear just once, even if shortcodes are invoked multiple times per page. Included code should preferably also be located towards the top of the document. The 11ty Bundle plugin

## Apple's Antitrust Playbook

DevFeed: [Apple's Antitrust Playbook](<https://devfeed.tech/articles/apple-s-antitrust-playbook-26556.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/09/apples-antitrust-playbook/>)

Author: Alex Russell

Published: 2025-09-25T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [iOS](<https://devfeed.tech/topics/ios.md>), [PWA](<https://devfeed.tech/topics/pwa.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Push Notifications](<https://devfeed.tech/topics/push-notifications.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [antitrust](<https://devfeed.tech/tags/antitrust.md>), [apis](<https://devfeed.tech/tags/apis.md>), [apple](<https://devfeed.tech/tags/apple.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [competition](<https://devfeed.tech/tags/competition.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [dma](<https://devfeed.tech/tags/dma.md>), [eu](<https://devfeed.tech/tags/eu.md>), [features](<https://devfeed.tech/tags/features.md>), [ios](<https://devfeed.tech/tags/ios.md>), [law](<https://devfeed.tech/tags/law.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [security](<https://devfeed.tech/tags/security.md>), [security-and-privacy](<https://devfeed.tech/tags/security-and-privacy.md>), [shipping](<https://devfeed.tech/tags/shipping.md>), [us](<https://devfeed.tech/tags/us.md>), [user](<https://devfeed.tech/tags/user.md>), [web](<https://devfeed.tech/tags/web.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The excerpt argues that Apple is blaming EU Digital Markets Act enforcement for limits on EU features while the author attributes those limits to Apple's own choices and alleged non-compliance. It says Apple previously threatened to remove PWAs in response to regulation and describes barriers to browser competition: restricting browser choice geographically, requiring separate downloads for improved browser versions, withholding PWA and push notification APIs, providing a faulty SDK, and making developer entitlements difficult to obtain. The author also alleges that Apple's browsers lack basic security and privacy controls and that Apple misrepresents its compliance. These are claims made by the excerpt; it ends before the author's account is complete.

### Source excerpt

Contents Lies by Any Other Name Great Artists Steal Dear 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 tear Apple down. But just when I thought I was out, they pull me back in. Over the past 24 hours, Cupertino has played the hits from its iPhone-era anti-user, anti-business, anti-rule-of-law power trip. To recap: Apple sent a demand that the EU give up on DMA enforcement in a petulant and utterly misleading press release that mostly served to catalogue Apple's own failures to comply. Cupertino's kept astroturf outfit -- ACT | The App Association -- penned unhinged misinformation for consumption by US regulatory types (h/t Damien Geradin). The EC then called Apple's bluff. Make no mistake about what's going on: Apple is claiming that the EU is forcing Apple to adopt interpretations of the DMA that no other party has, which the EC itself has not backed, and which are "forcing" Apple to avoid shipping features in the EU. Or, put another way, Apple wants to launder the consequences of its own anticompetitive, anti-user choices through a credulous tech press. The goal is to frame regulators for Apple's own deeds. Lies by Any Other Name If this smells like bullshit, that's because it is. Apple tried similar ploys last year when it sprung a blatant attempt to kill PWAs on the EU as a price for having the temerity to regulate. The plan, it seemed then, was to adopt an exotic reading of the DMA and frame the EC for killing PWAs. What Apple's attempting now is even more brazen, particularly after 16+ months of serial non-compliance since the DMA came into force (h/t OWA). Remember that: Apple's browser, and by extension every iOS browser, fails on basic security and privacy controls, putting users at risk constantly. Apple serially misrepresents this situation to anyone who will

## Apple's WebKit Feature Pace and Browser Competition on iOS

DevFeed: [Apple's WebKit Feature Pace and Browser Competition on iOS](<https://devfeed.tech/articles/comforting-myths-26558.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/09/cupertinos-comforting-myths/>)

Author: Alex Russell

Published: 2025-09-23T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [WebKit](<https://devfeed.tech/topics/webkit.md>), [browser](<https://devfeed.tech/topics/browser.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Web](<https://devfeed.tech/topics/web.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [features](<https://devfeed.tech/tags/features.md>), [standards](<https://devfeed.tech/tags/standards.md>), [web](<https://devfeed.tech/tags/web.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

This opinion article examines Apple's approach to web-platform collaboration and feature development, arguing that WebKit has trailed Blink and Gecko while Apple's iOS policies prevent competing browsers from shipping alternative engines. It introduces data intended to assess claims about Apple's handling of challenging APIs.

### Source excerpt

Update: The charts below were inappropriately snapped, compressing the range of values. This has been corrected. Feature availability numbers also changed since drafting and have been updated. In several recent posts, I've attempted to address how the structure of standards bodies and their adjacent incubation venues accelerates or suppresses the potential of the web as a platform. The pace of progress matters because platforms are competitions, and actors that prevent expansions of basic capabilities risk consigning the web to the dustbin. Inside that framework, there is much to argue over regarding the relative merits of specific features and evolutionary directions. This is healthy and natural. We should openly discuss features and their risks, try to prevent bad consequences, and work to mend what breaks. This competitive process has made browsers incredibly safe and powerful for 30 years. Until iOS, that is. Imagine my surprise upon hearing that Apple isn't attempting to freeze the web in amber, preserving advantages for its proprietary platform, and that it instead offers to redesign proposals it disagrees with. Contents Background Is Apple Engaged In Constructive API Redesign? General Trends Hard Cases Overall Impressions What's Happening Here? As I have occasionally documented, this has not been my experience. I have relatively broad exposure to the patterns of Apple's collaboration, having designed, advised on, or led teams that built dozens of features across disparate areas of the platform since the Blink fork.1 But perhaps this was the wrong slice from which to judge? I've been hearing of Apple's openness to collaboration on challenging APIs so often that either my priors are invalid, or something else is at work. To find out, I needed data. Background A specific parry gets deployed whenever WebKit's sluggish feature pace comes up: "controversial" features "lack consensus" or "are not standards" or "have privacy and security problems" (unspecified). The

## Web Standards and the Fall of the House of Iamus

DevFeed: [Web Standards and the Fall of the House of Iamus](<https://devfeed.tech/articles/web-standards-and-the-fall-of-the-house-of-iamus-26559.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/09/standards-and-the-fall-of-iamus/>)

Author: Alex Russell

Published: 2025-09-21T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [web-standards](<https://devfeed.tech/topics/web-standards.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [WebKit](<https://devfeed.tech/topics/webkit.md>), [W3C](<https://devfeed.tech/topics/w3c.md>)

Tags: [browsers](<https://devfeed.tech/tags/browsers.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [commentary](<https://devfeed.tech/tags/commentary.md>), [competition](<https://devfeed.tech/tags/competition.md>), [design](<https://devfeed.tech/tags/design.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [ios](<https://devfeed.tech/tags/ios.md>), [launch](<https://devfeed.tech/tags/launch.md>), [leading](<https://devfeed.tech/tags/leading.md>), [license](<https://devfeed.tech/tags/license.md>), [mozilla](<https://devfeed.tech/tags/mozilla.md>), [patents](<https://devfeed.tech/tags/patents.md>), [process](<https://devfeed.tech/tags/process.md>), [responsibility](<https://devfeed.tech/tags/responsibility.md>), [shipping](<https://devfeed.tech/tags/shipping.md>), [standards](<https://devfeed.tech/tags/standards.md>), [web](<https://devfeed.tech/tags/web.md>), [web-standards](<https://devfeed.tech/tags/web-standards.md>), [webdev](<https://devfeed.tech/tags/webdev.md>), [webkit](<https://devfeed.tech/tags/webkit.md>)

### AI overview

The author argues that voluntary web standards do not decide which browser features ship or whether they are useful: vendors choose what to implement, and consensus cannot be a prerequisite for shipping. In this account, standards groups review and refine designs that have already been tried, then formalize them--sometimes years after initial release--to encourage adoption and reduce patent risk. The excerpt distinguishes responsible feature development from standardization, attributing it to thoughtful launch processes. It does not provide the article's full discussion.

### Source excerpt

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 it wants." This is true, of course, but not in the way commenters intend; and not only because Blink's rigorous launch process frequently prevents unvalidated designs from shipping. Except for iOS, where Apple attempts to hide its role in undermining the competitive foundation of web standards, every vendor always ships "whatever it wants." That is the point of voluntary standards, and competition is the wind in those sails. Working Groups don't gate what browsers ship, nor do they define what's useful or worthy. There are no seers; no Delphic oracles that fleetingly glimpse a true logos. Working Groups do not invent the future, nor do they hand down revealed truths like prophets of the House of Iamus. In practice, they are thoughtful historians of recent design expeditions, critiquing, tweaking, then spreading the good news of proposals that already work through Web Standards ratified years after features first ship, serving to licence designs liberally to increase their spread. In the end, this is the role of standards and the Working Groups that develop them: to license patents that read on existing designs, reducing risks to implementers who adopt them. Anyone who tries to convince you otherwise, or invites you to try your hand at invention within a chartered Working Group, does not understand what those groups are designed to do. Sadly, this includes some folks who spend a lot of time in them. Contents Terminology Traps Standardisation != Interoperability Standardisation != Responsibility What Working Groups Really Do Chartered Working Groups Are Not Design Venues The Role of Incubation No Prophecies, Only Engineering Complaints about certain engines leading

## Apple's Assault on Standards

DevFeed: [Apple's Assault on Standards](<https://devfeed.tech/articles/apple-s-assault-on-standards-26557.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/09/apples-crimes-against-the-internet-community/>)

Author: Alex Russell

Published: 2025-09-02T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Web platform](<https://devfeed.tech/topics/web-platform.md>), [Web](<https://devfeed.tech/topics/web.md>), [centralization](<https://devfeed.tech/topics/centralization.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [choice](<https://devfeed.tech/tags/choice.md>), [competition](<https://devfeed.tech/tags/competition.md>), [governance](<https://devfeed.tech/tags/governance.md>), [internet](<https://devfeed.tech/tags/internet.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [markets](<https://devfeed.tech/tags/markets.md>), [power](<https://devfeed.tech/tags/power.md>), [software](<https://devfeed.tech/tags/software.md>), [standards](<https://devfeed.tech/tags/standards.md>), [users](<https://devfeed.tech/tags/users.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The excerpt argues that internet standards depend on functioning competition: interoperability helps users switch software, limits vendor lock-in, and distributes power toward users. It says standards bodies built on assumptions that operating systems would be open and software could be replaced cheaply, making it easier to bring different software to a device. The author contends that Apple has engineered a situation in which changing browsers can require replacing hardware, undermining user choice and the competitive role standards are meant to serve. The excerpt frames standards as both an economic and political means of limiting concentrated corporate power.

### Source excerpt

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. Apple has poisoned the well through a monopoly on influence, which it has parleyed into suppression of browser choice. This is an existential threat to the web, but also renders web and internet standards moot. Internet standards bodies should recognise the threat and respond. Contents The Power of Interoperability Voluntary Adoption Is Foundational to Internet Standards Apple's Unique Monopoly How Apple Uses Its Monopoly to Centralise and Enclose Apple's Transgressions Against Voluntary Adoption Unilateral Off-Ramps How Apples Crimes Differ From Prior Episodes Necessary, Proportional Responses Why Now? Do Standards Matter? Internet enthusiasts of the previous century sometimes expressed the power of code by declaring the sovereignty of cyberspace, or that "code is law." As odd as these claims sound today, they hit a deep truth: end-users, and even governments, lack power to re-litigate choices embodied in software. Software vendors, therefore, have power. Backed by deeply embedded control chokepoints, and without a proportional response from other interests, this control is akin to state power. Both fear and fervour about these properties developed against a backdrop of libertarian1 attitudes toward regulation and competition. Attenuating vendor power through interoperability was, among other values, a shared foundation of collaboration for internet pioneers. The most fervent commitment of this strain was faith in markets to sort out information distribution problems through pricing signals,2 and that view became embedded deeply into the internet's governance mechanisms.3 If competition does not function, neither do standards. The internet's most consequential

## Apple's in-app browsers may enable extensive tracking despite App Tracking Transparency

DevFeed: [Apple's in-app browsers may enable extensive tracking despite App Tracking Transparency](<https://devfeed.tech/articles/apple-vs-facebook-is-kayfabe-26553.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/08/apple-vs-fb-kayfabe/>)

Author: Alex Russell

Published: 2025-08-25T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [WebView](<https://devfeed.tech/topics/webview.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Web](<https://devfeed.tech/topics/web.md>), [Internet](<https://devfeed.tech/topics/internet.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [facebook](<https://devfeed.tech/tags/facebook.md>), [in-app-browsers](<https://devfeed.tech/tags/in-app-browsers.md>), [internet](<https://devfeed.tech/tags/internet.md>), [policy](<https://devfeed.tech/tags/policy.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [script](<https://devfeed.tech/tags/script.md>), [surveillance](<https://devfeed.tech/tags/surveillance.md>), [web](<https://devfeed.tech/tags/web.md>), [webview](<https://devfeed.tech/tags/webview.md>)

### AI overview

The article argues that Apple's App Tracking Transparency had little discernible effect on Facebook's revenue and that Apple continues to permit extensive tracking through in-app browsers. It says these WebViews can observe URLs and allow existing web tracking mechanisms to correlate in-app activity with browsing, while restricting users' access to their preferred browsers.

### Source excerpt

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" rolled out, talking up the impact to Facebook's business. But San Mateo's profits tell a very different story. Net income dipped between late 2021 and early 2023 thanks to accelerating capital expenditures, not reductions in revenue. Despite strenuous efforts to sell the move, it's hard to discern any impact from ATT whatsoever. How can we be sure Apple's wise? Because Cupertino continues to allow Facebook's wide-scale abuse of In-App Browsers: Open Web Advocacy - In-App Browser Primer Apple has long facilitated and enriched mass surveillance through native apps, both directly from in-app activity, but much more insidiously through the In-App Browsers that lurk behind every link in Facebook, Instagram, Messenger, Threads, TikTok, Pinterest, etc. I have written about them before, and they still stink to high heavens. Facebook couldn't ask for a better or more willing accomplice than Apple as it glides into the second decade of its browserjacking spree. In-App Browsers are, for Facebook's purposes, ad-blocker blockers. Cheat codes for the enterprising panopticon proprietor. Much wringing of hands transpires every time one of these knockoff browsers is suspected of injecting script into web pages. The fear is that this will enable a level of tracking by apps that is not otherwise possible. As scary (and real) as the threat is, it is also a misdirection. To effect total surveillance, Facebook et al. don't need to inject scripts into the runtime, they only need your browser not to block their "ad tags" that are already embedded in every high-traffic page on the internet. Combined with the ability to watch every URL you navigate to in a WebView, this is more than enough to

## How Do Committees Fail To Invent?

DevFeed: [How Do Committees Fail To Invent?](<https://devfeed.tech/articles/how-do-committees-fail-to-invent-26554.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/08/how-do-committees-fail-to-invent/>)

Author: Alex Russell

Published: 2025-08-11T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [software-development](<https://devfeed.tech/topics/software-development.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [W3C](<https://devfeed.tech/topics/w3c.md>)

Tags: [browsers](<https://devfeed.tech/tags/browsers.md>), [code](<https://devfeed.tech/tags/code.md>), [column](<https://devfeed.tech/tags/column.md>), [communication](<https://devfeed.tech/tags/communication.md>), [conway](<https://devfeed.tech/tags/conway.md>), [conway-s-law](<https://devfeed.tech/tags/conway-s-law.md>), [delegates](<https://devfeed.tech/tags/delegates.md>), [design](<https://devfeed.tech/tags/design.md>), [designs](<https://devfeed.tech/tags/designs.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [fail](<https://devfeed.tech/tags/fail.md>), [law](<https://devfeed.tech/tags/law.md>), [mirror](<https://devfeed.tech/tags/mirror.md>), [open](<https://devfeed.tech/tags/open.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [paper](<https://devfeed.tech/tags/paper.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [prevent](<https://devfeed.tech/tags/prevent.md>), [problems](<https://devfeed.tech/tags/problems.md>), [progress](<https://devfeed.tech/tags/progress.md>), [solution](<https://devfeed.tech/tags/solution.md>), [standards](<https://devfeed.tech/tags/standards.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

In standards development organizations, a small minority with veto power can stall designs that most participants support. The excerpt calls this the "fifth column problem": delegates may object spuriously, stay silent about their intentions, or delay consideration while their firms' willingness to implement remains unclear. Open membership can make such behavior easier, while group rules or norms that create many veto players turn poor communication into a blockage. The resulting delays can leave important features out of standards and weaken web developers' confidence in them. The excerpt ends mid-sentence, so it does not establish what remedies or further consequences the full article presents.

### Source excerpt

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 leaders ignore at their peril, and everyone who delivers code for a living benefits from a (re)read of "The Mythical Man-Month", available at fine retailers everywhere. Conway's Law is generally invoked to describe organisations working to solve well-defined problems, in which everyone is working towards a solution. But what if there are defectors? And what if they can prevent forward progress without paying any price? This problem is rarely analysed for the simple reason that such an organisation would be deranged. But what if that happened regularly? I was reminded of the possibility while chatting with a colleague joining a new (to them) Working Group at the W3C. The most cursed expressions of Conway's Law regularly occur in Standards Development Organisations (SDOs); specifically, when delegates refuse to communicate their true intentions, either through spurious objection or tactical silence. This special case is the fifth column problem. Contents How Does This Happen? Mayfly Half-Lives The Web Platform's Power Structure But Why? Problem Misstatements Closed For Business Survivorship Bias and The Problem of Big, Old Rooms Marketing Gridlock As Thoughtfulness When Is A "Consensus" Not Consensus? Defences Against Fifth Columns Expressed in Conwayist terms, the fifth column problem describes the way organisations mirror the miscommunication patterns of their participants when they fail to deliver designs of any sort. This pathology presents when the goal of the majority is antithetical to a small minority with a veto. Reticence of certain SDO participants to consider important problems is endemic, in part, due to open membership. Unlike corporate environments wh

## Links? Links!

DevFeed: [Links? Links!](<https://devfeed.tech/articles/links-links-26552.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/07/links/>)

Author: Alex Russell

Published: 2025-07-16T00:00:00Z

Content type: article

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Web Development](<https://devfeed.tech/topics/web-development.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [static-site-generator](<https://devfeed.tech/topics/static-site-generator.md>), [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>), [CSS Framework](<https://devfeed.tech/topics/css-framework.md>)

Tags: [11ty](<https://devfeed.tech/tags/11ty.md>), [astro](<https://devfeed.tech/tags/astro.md>), [blogs](<https://devfeed.tech/tags/blogs.md>), [community](<https://devfeed.tech/tags/community.md>), [css](<https://devfeed.tech/tags/css.md>), [culture](<https://devfeed.tech/tags/culture.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [html](<https://devfeed.tech/tags/html.md>), [links](<https://devfeed.tech/tags/links.md>), [list](<https://devfeed.tech/tags/list.md>), [performance](<https://devfeed.tech/tags/performance.md>), [platform](<https://devfeed.tech/tags/platform.md>), [reading](<https://devfeed.tech/tags/reading.md>), [resources](<https://devfeed.tech/tags/resources.md>), [svg](<https://devfeed.tech/tags/svg.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The author created a links and resources page for performance- and platform-oriented web development, combining frequently shared resources, background reading and a blogroll. It includes more than 250 links and an OPML export for downloading or sending to a feed reader; finding blog and feed links required substantial manual work. While collecting them, the author observed that creative CSS, HTML and SVG work can thrive in modern browsers without large legacy frameworks, and that 11ty and Astro are common among the personal sites of talented frontend developers. They also praise polished RSS/Atom previews and note signs of continued web whimsy, including webrings, guestbooks and ASCII art. The excerpt ends mid-thought.

### Source excerpt

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 sounds like procrastination, well, you might very well think that. I couldn't possibly comment. The result is a new links and resources page page which you can find over in the navigation rail. It's part list-of-things-I-keep-sending-people, part background reading, and part blogroll. The blogroll section also prompted me to create an OPML export , which you can download or send directly to your feed reader of choice. The page now contains more than 250 pointers to people and work that I view as important to a culture that is intentional about building a web worth wanting. Hopefully maintenance won't be onerous from here on in. The process of tracking down links to blogs and feeds is a slog, no matter how good the tooling. Very often, this involved heading to people's sites and reading the view-source:// FOMO Having done this dozens of times on the sites of brilliant and talented web developers in a short period of time, a few things stood out. First -- and I cannot emphasise this enough -- holy cow. The things creative folks can do today with CSS, HTML, and SVG in good browsers is astonishing. If you want to be inspired about what's possible without dragging bloated legacy frameworks along, the work of Ana Tudor, Jhey, Julia Miocene, Bramus, Adam, and so many others can't help but raise your spirits. The CodePen community, in particular, is incredible, and I could (and have) spend hours just clicking through and dissecting clever uses of the platform from the site's "best of" links. Second, 11ty and Astro have won the hearts of frontend's best minds. It's not universal, but the overwhelming bulk of personal pages by the most talented frontenders are now built with SS

## Conferences, Clarity, and Smokescreens

DevFeed: [Conferences, Clarity, and Smokescreens](<https://devfeed.tech/articles/conferences-clarity-and-smokescreens-26550.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/06/conferences-clarity-and-smokescreens/>)

Author: Alex Russell

Published: 2025-06-27T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Developer Events](<https://devfeed.tech/topics/developer-events.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [accessibility](<https://devfeed.tech/tags/accessibility.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [community](<https://devfeed.tech/tags/community.md>), [conference](<https://devfeed.tech/tags/conference.md>), [conferences](<https://devfeed.tech/tags/conferences.md>), [consulting](<https://devfeed.tech/tags/consulting.md>), [data](<https://devfeed.tech/tags/data.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [framework](<https://devfeed.tech/tags/framework.md>), [hacks](<https://devfeed.tech/tags/hacks.md>), [lighting](<https://devfeed.tech/tags/lighting.md>), [performance](<https://devfeed.tech/tags/performance.md>), [recommended](<https://devfeed.tech/tags/recommended.md>), [schedule](<https://devfeed.tech/tags/schedule.md>), [sort](<https://devfeed.tech/tags/sort.md>), [speakers](<https://devfeed.tech/tags/speakers.md>), [stream](<https://devfeed.tech/tags/stream.md>), [summit](<https://devfeed.tech/tags/summit.md>), [talk](<https://devfeed.tech/tags/talk.md>), [talks](<https://devfeed.tech/tags/talks.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The author contrasts JSNation's evidence-focused debate and talks on outdated browser hacks, LoAF, and accessibility with React Summit 2025, whose program they say largely reinforced frameworkist views. They argue conference agendas reveal which community narratives leaders want debated, and contend that React Summit did not surface the React community's measurable quality crisis to attendees who were unaware of it. The excerpt ends as the author begins to explain how to distinguish engineering conferences from marketing events, so that explanation is not available here.

### Source excerpt

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. The conference venue was lovely, and speakers were more than well looked after. Many of the JSNation talks were of exactly the sort I'd hope to see as our discipline belatedly confronts a lost decade, particularly Jeremias Menichelli's lighting talk. It masterfully outlined how many of the hacks we have become accustomed to are no longer needed, even in the worst contemporary engines. view-source:// on the demo site he made to see what I mean. Vinicius Dallacqua's talk on LoAF was on-point, and the full JSNation line-up included knowledgeable and wise folks, including Jo, Charlie, Thomas, Barry, Nico, and Eva. There was also a strong set of accessibility talks from presenters I'm less familiar with, but whose topics were timely and went deeper than the surface. They even let me present a spicier topic than I think they might have been initially comfortable with. All-in-all, JSNation was a lovely time, in good company, with a strong bent toward doing a great job for users. Recommended. Day 21 -- React Summit 2025 -- could not have been more different. While I was in a parallel framework authors meeting for much of the morning,2 I did attend talks in the afternoon, studied the schedule, and went back through many more after the fact on the stream. Aside from Xuan Huang's talk on Lynx and Luca Mezzalira's talk on architecture, there was little in the program that challenged frameworkist dogma, and much that played to it. This matters because conferences succeed by foregrounding the hot topics within a community. Agendas are curated to reflect the tides of debate in the zeitgeist, and can be read as a map of the narratives a community's leaders wish to see debated. My da

## Safari at WWDC '25: The Ghost of Christmas Past

DevFeed: [Safari at WWDC '25: The Ghost of Christmas Past](<https://devfeed.tech/articles/safari-at-wwdc-25-the-ghost-of-christmas-past-26551.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/06/the-ghost-of-christmas-past/>)

Author: Alex Russell

Published: 2025-06-13T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [browser](<https://devfeed.tech/topics/browser.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [web animation](<https://devfeed.tech/topics/web-animation.md>)

Tags: [anchor-positioning](<https://devfeed.tech/tags/anchor-positioning.md>), [animations](<https://devfeed.tech/tags/animations.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [apple](<https://devfeed.tech/tags/apple.md>), [audio](<https://devfeed.tech/tags/audio.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [competition](<https://devfeed.tech/tags/competition.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [css](<https://devfeed.tech/tags/css.md>), [features](<https://devfeed.tech/tags/features.md>), [file-system](<https://devfeed.tech/tags/file-system.md>), [hdr](<https://devfeed.tech/tags/hdr.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [resource-management](<https://devfeed.tech/tags/resource-management.md>), [safari](<https://devfeed.tech/tags/safari.md>), [scroll-driven-animations](<https://devfeed.tech/tags/scroll-driven-animations.md>), [svg](<https://devfeed.tech/tags/svg.md>), [webdev](<https://devfeed.tech/tags/webdev.md>), [wwdc](<https://devfeed.tech/tags/wwdc.md>)

### AI overview

The author characterizes Safari's WWDC '25 announcement as mostly catch-up: nearly all listed features had already shipped in Chromium, with some available earlier through Origin Trials. Apple may lead on a smaller set, including Digital Credentials API, CSS contrast-color(), margin-trim extensions, ALAC recording, and Audio Output Devices API, but the author notes that Safari's announcement is for a beta and Chromium timing is uncertain. The excerpt argues that Safari's feature gaps affect all iOS browsers and describes Apple's response to EU browser-engine choice requirements as obstructive, citing threats to end PWAs, inadequate or broken APIs, and onerous proposed terms. The supplied text cuts off during this criticism.

### Source excerpt

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: 2023: WebGPU 2020: SVG Favicons 2023: HDR Images 2024: CSS Anchor Positioning 2023: CSS text-wrap: pretty 2025: CSS progress() function 2023: Scroll-driven Animations (finally!!!) 2020: Trusted Types 2021: URL Pattern API early 2025: WebAuthN Signal API 2020: WritableStreams for the File System APIs late 2023: Scroll Margin for Intersection Observers 2025: CSS Logical Overflow (overflow-block and overflow-inline) 2024: CSS align-self and justify-self in absolute positioning 2025: a subset of Explicit JavaScript Resource Management 2021: AudioEncoder & AudioDecoder for WebCodecs 2020: RTCEncodedAudioFrame & RTCEncodedVideoFrame serialisation 2024: RTCEncodedAudioFrame & RTCEncodedVideoFrame constructors 2018: PCM format support in MediaRecorder 2017: ImageCapture.grabFrame() 2017(?): SVG pointer-events="bounding-box" 2015: <link rel=dns-prefetch> In many cases, these features were available to developers even earlier via the Origin Trials mechanism. WebGPU, e.g., ran trials for a year, allowing developers to try the in-development feature on live sites in Chrome and Edge as early as September 2021. There are features that Apple appears to be leading on in this release, but it's not clear that they will become available in Safari before Chromium-based browsers launch them, given that the announcement is about a beta: Digital Credentials API: currently in Chromium OT. CSS contrast-color() margin-trim: block inline extends a neat Safari-only feature in useful ways. Apple's ALAC format for MediaRecorder. Audio Output Devices API. In progress in Chromium, but no launch scheduled. The announced support for CSS image crossorigin() and referrerpolicy() modifiers has an unclear

## If Not React, Then What?

DevFeed: [If Not React, Then What?](<https://devfeed.tech/articles/if-not-react-then-what-26549.md>)

Original publisher: [Read original article](<https://infrequently.org/2024/11/if-not-react-then-what/>)

Author: Alex Russell

Published: 2024-11-29T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [React](<https://devfeed.tech/topics/react.md>), [legacy systems](<https://devfeed.tech/topics/legacy-systems.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [inclusive design](<https://devfeed.tech/topics/inclusive-design.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [advocacy](<https://devfeed.tech/tags/advocacy.md>), [apis](<https://devfeed.tech/tags/apis.md>), [applications](<https://devfeed.tech/tags/applications.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [frameworkism](<https://devfeed.tech/tags/frameworkism.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [legacy-technology](<https://devfeed.tech/tags/legacy-technology.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [modern](<https://devfeed.tech/tags/modern.md>), [performance](<https://devfeed.tech/tags/performance.md>), [products](<https://devfeed.tech/tags/products.md>), [project](<https://devfeed.tech/tags/project.md>), [react](<https://devfeed.tech/tags/react.md>), [research](<https://devfeed.tech/tags/research.md>), [server](<https://devfeed.tech/tags/server.md>), [team](<https://devfeed.tech/tags/team.md>), [the-web](<https://devfeed.tech/tags/the-web.md>), [web](<https://devfeed.tech/tags/web.md>), [web-apis](<https://devfeed.tech/tags/web-apis.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The author argues against starting new projects with React, based on experience remediating performance and accessibility problems in modern frontend stacks, especially React-based ones. Their central principle is to minimize client-side complexity: server code and resources are more controllable, while client conditions and API availability are not. They recommend sending less code and favoring HTML and CSS over JavaScript, which they say can deliver UI with greater resilience and better compression. The excerpt begins comparing React and other frameworks but ends before supplying further details or alternatives.

### Source excerpt

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 most of this time working through improvements to web APIs, the majority of time spent with partners goes to remediating performance and accessibility issues caused by "modern" frontend frameworks and the culture surrounding them. Today, these issues are most pronounced in React-based stacks. This is disquieting because React is legacy technology, but it continues to appear in greenfield applications. Surprisingly, some continue to insist that React is "modern." Perhaps we can square the circle if we understand "modern" to apply to React in the way it applies to art. Neither demonstrate contemporary design and construction. They are not built for current needs and do not meet contemporary performance standards, but pose as expensive objets harkening back to an earlier era's antiquated methods. Contents The Rule Of Least Client-Side Complexity OK, But What, Then? And Nothing Of Value Was Lost Vignettes Informational E-Commerce Media Social Productivity Other Application Classes "But..." "...we need to move fast" "...it works for Facebook" "...our teams already know React" "...we need to be able to hire easily" "...everyone has fast phones now" "...React is industry-standard" "...the ecosystem..." "...Next.js can be fast (enough)" "...React Native!" References In the hope of steering the next team away from the rocks, I've found myself penning advocacy pieces and research into the state of play, as well as giving talks to alert managers and developers of the dangers of today's frontend orthodoxy. In short, nobody should start a new project in the 2020s based on React. Full stop.1 The Rule Of Least Client-Side Complexity Code that runs on the server can be fully costed. Pe

## Platform Strategy and Its Discontents

DevFeed: [Platform Strategy and Its Discontents](<https://devfeed.tech/articles/platform-strategy-and-its-discontents-26548.md>)

Original publisher: [Read original article](<https://infrequently.org/2024/10/platforms-are-competitions/>)

Author: Alex Russell

Published: 2024-10-27T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Community, Industry, State of the Web, Web Strategy](<https://devfeed.tech/topics/community-industry-state-of-the-web-web-strategy.md>), [Business, Industry, Usability, User Experience, User Research, Web Strategy](<https://devfeed.tech/topics/business-industry-usability-user-experience-user-research-web-strategy.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [PWA](<https://devfeed.tech/topics/pwa.md>), [React](<https://devfeed.tech/topics/react.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>)

Tags: [browsers](<https://devfeed.tech/tags/browsers.md>), [community](<https://devfeed.tech/tags/community.md>), [competition](<https://devfeed.tech/tags/competition.md>), [consulting](<https://devfeed.tech/tags/consulting.md>), [cost](<https://devfeed.tech/tags/cost.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [ecosystems](<https://devfeed.tech/tags/ecosystems.md>), [failure](<https://devfeed.tech/tags/failure.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [js](<https://devfeed.tech/tags/js.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [native](<https://devfeed.tech/tags/native.md>), [performance](<https://devfeed.tech/tags/performance.md>), [phones](<https://devfeed.tech/tags/phones.md>), [platform](<https://devfeed.tech/tags/platform.md>), [react](<https://devfeed.tech/tags/react.md>), [speed](<https://devfeed.tech/tags/speed.md>), [strategy](<https://devfeed.tech/tags/strategy.md>), [teams](<https://devfeed.tech/tags/teams.md>), [web-developers](<https://devfeed.tech/tags/web-developers.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The author argues that JavaScript-first web development is making phone experiences less usable and more costly, despite its promise of write-once, test-everywhere development. Drawing on a decade helping teams build competitive PWAs, they say failure rates rose as teams relied on desktop-oriented tools without checking how well they handled mobile constraints. They contrast this with native developers' deliberate adjustment to mobile, which can require multiple codebases but, in their account, delivers speed for the added cost. The author frames this as a platform competition: the web should let people do most daily tasks in a browser that is easier, faster, and more secure, with time spent on the platform offered as one possible measure. The excerpt does not include the post's further reasoning or recommendations.

### Source excerpt

This post is an edited and expanded version of a now-mangled Mastodon thread. Contents Platforms Are Competitions ...and We're Losing Win Condition You Do It To Yourself, And That's What Really Hurts Groundhog Day Reboot Some in the JavaScript community imagine that I harbour an irrational dislike of their tools when, in fact, I want nothing more than to stop thinking about them. Live-and-let-live is excellent guidance, and if it weren't for React et. al.'s predictably ruinous outcomes, the public side of my work wouldn't involve educating about the problems JS-first development has caused. But that's not what strategy demands, and strategy is my job.1 I've been holding my fire (and the confidences of consulting counterparties) for most of the last decade. Until this year, I only occasionally posted traces documenting the worsening rot. I fear this has only served to make things look better than they are. Over the past decade, my work helping teams deliver competitive PWAs gave me a front-row seat to a disturbing trend. The rate of failure to deliver usable experiences on phones was increasing over time, despite the eye-watering cost of JS-based stacks teams were reaching for. Worse and costlier is a bad combo, and the opposite of what competing ecosystems did. Native developers reset hard when moving from desktop to mobile, getting deeply in touch with the new constraints. Sure, developing a codebase multiple times is more expensive than the web's write-once-test-everywhere approach, but at least you got speed for the extra cost. That's not what web developers did. Contemporary frontend practice pretended that legacy-oriented, desktop-focused tools would perform fine in this new context, without ever checking if they did. When that didn't work, the toxic-positivity crowd blamed the messenger.2 Frontend's tragically timed turn towards JavaScript means the damage isn't limited to the public sector or "bad" developers. Some of the strongest engineers I know find thems

## Reckoning: Part 4 -- The Way Out

DevFeed: [Reckoning: Part 4 -- The Way Out](<https://devfeed.tech/articles/reckoning-part-4-the-way-out-26547.md>)

Original publisher: [Read original article](<https://infrequently.org/2024/08/the-way-out/>)

Author: Alex Russell

Published: 2024-08-16T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Business, Industry, Usability, User Experience, User Research, Web Strategy](<https://devfeed.tech/topics/business-industry-usability-user-experience-user-research-web-strategy.md>), [ui-testing](<https://devfeed.tech/topics/ui-testing.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>)

Tags: [browsers](<https://devfeed.tech/tags/browsers.md>), [disaster](<https://devfeed.tech/tags/disaster.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [history-of-computing](<https://devfeed.tech/tags/history-of-computing.md>), [industry](<https://devfeed.tech/tags/industry.md>), [it](<https://devfeed.tech/tags/it.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [mainframes](<https://devfeed.tech/tags/mainframes.md>), [marketing](<https://devfeed.tech/tags/marketing.md>), [performance](<https://devfeed.tech/tags/performance.md>), [prevent](<https://devfeed.tech/tags/prevent.md>), [procurement](<https://devfeed.tech/tags/procurement.md>), [production](<https://devfeed.tech/tags/production.md>), [queue](<https://devfeed.tech/tags/queue.md>), [series](<https://devfeed.tech/tags/series.md>), [smartphones](<https://devfeed.tech/tags/smartphones.md>), [snap](<https://devfeed.tech/tags/snap.md>), [teams](<https://devfeed.tech/tags/teams.md>), [user](<https://devfeed.tech/tags/user.md>), [users](<https://devfeed.tech/tags/users.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The excerpt argues that excessive JavaScript and poor performance result from choices across a site's production chain, and that one advocate can help redirect a project toward users. It recommends that engineering managers, product managers, and tech leads agree on common user journeys, document them end to end, automate tests (for example, with WebPageTest.org's scripting system), and track journey-level performance in dashboards. The excerpt says these steps can help, while cautioning that there is no single solution.

### Source excerpt

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 falling use of the web on smartphones.1 Public data shows what I warned about, citing Google-private data, in 2019. In the US, time spent in browsers continues to stagnate while smartphone use grows, and the situation is even more dire outside the states. The result is a falling fraction of time spent. This is not a recipe for a healthy web. If nothing changes, eventually, the web will become a footnote in the history of computing; a curio along side mainframes and minicomputers -- never truly gone but lingering with an ashen palour and a necrotic odour. We don't have to wait to see how this drama plays out to understand the very real consequences of JavaScript excess on users.2 Contents Managers Engineers and Designers Public Sector Agencies Values Matter Everyone in a site's production chain has agency to prevent disaster. Procurement leads, in-house IT staff, and the managers, PMs, and engineers working for contractors and subcontractors building the SNAP sites we examined all had voices that were more powerful than the users they under-served. Any of them could have acted to steer the ship away from the rocks. Unacceptable performance is the consequence of a chain of failures to put the user first. Breaking the chain usually requires just one insistent advocate. Disasters like BenefitsCal are not inevitable. The same failures play out in the commercial teams I sit with day-to-day. Failure is not a foregone conclusion, yet there's an endless queue of sites stuck in the same ditch, looking for help to pull themselves out. JavaScript overindulgence is always an affirmative decision, no matter how hard industry "thought leaders" gaslight us. Marketing that casts highly

## Reckoning: Part 3 -- Caprock

DevFeed: [Reckoning: Part 3 -- Caprock](<https://devfeed.tech/articles/reckoning-part-3-caprock-26544.md>)

Original publisher: [Read original article](<https://infrequently.org/2024/08/caprock/>)

Author: Alex Russell

Published: 2024-08-14T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Front end](<https://devfeed.tech/topics/frontend.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>), [digital experience monitoring](<https://devfeed.tech/topics/digital-experience-monitoring.md>)

Tags: [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [boston](<https://devfeed.tech/tags/boston.md>), [california](<https://devfeed.tech/tags/california.md>), [client](<https://devfeed.tech/tags/client.md>), [code](<https://devfeed.tech/tags/code.md>), [complex](<https://devfeed.tech/tags/complex.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [critical](<https://devfeed.tech/tags/critical.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [defects](<https://devfeed.tech/tags/defects.md>), [delivered](<https://devfeed.tech/tags/delivered.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [deloitte](<https://devfeed.tech/tags/deloitte.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [devices](<https://devfeed.tech/tags/devices.md>), [errors](<https://devfeed.tech/tags/errors.md>), [performance](<https://devfeed.tech/tags/performance.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The excerpt argues that client-side JavaScript makes public SNAP application sites harder to access and operate, especially over slow networks and on low-end devices. It says JavaScript-heavy architectures add complex, expensive tools; JavaScript requires more processing than HTML and CSS and can prevent browsers from parallelizing page loading. Single-page-application stacks also preload code for later interactions, and limiting that extra code takes effort. The author argues these factors put JavaScript on the critical path at a disadvantage compared with HTML-first progressive enhancement, while attributing the sites' problems partly to procurement and organizational capacity. The excerpt ends during a discussion of mobile-device constraints.

### Source excerpt

Other posts in the series: Reckoning: Part 1 -- The Landscape Reckoning: Part 2 -- Object Lesson Reckoning: Part 4 -- The Way Out Contents Complexity Perplexity Carrying Capacity Should This Be An SPA? The Pits Aftermath Last time, we looked at how JavaScript-based web development compounded serving errors on US public sector service sites, slowing down access to critical services. These defects are not without injury. The pain of accessing SNAP assistance services in California, Massachusetts, Maryland, Tennessee, New Jersey, and Indiana likely isn't dominated by the shocking performance of their frontends, but their glacial delivery isn't helping. Waits are a price that developers ask users to pay and loading spinners only buy so much time. Complexity Perplexity These SNAP application sites create hurdles to access because the departments procuring them made or green-lit inappropriate architecture choices. In fairness, those choices may have seemed reasonable given JavaScript-based development's capture of the industry. Betting on JavaScript-based, client-side rendered architectures leads to complex and expensive tools. Judging by the code delivered over the wire, neither CalSAWS nor Deloitte understand those technologies well enough to operate them proficiently. From long experience and a review of the metrics (pdf) the CalSAWS Joint Management Authority reports, it is plain as day that the level of organisational and cultural sophistication required to deploy a complex JavaScript frontend is missing in Sacramento: Dora Militaru | Performance culture through the looking-glass It's safe to assume a version of the same story played out in Annapolis, Nashville, Boston, Trenton, and Indianapolis. JavaScript-based UIs are fundamentally more challenging to own and operate because the limiting factors on their success are outside the data center and not under the control of procuring teams. The slow, flaky networks and low-end devices that users bring to the party define t

## Reckoning: Part 2 -- Object Lesson

DevFeed: [Reckoning: Part 2 -- Object Lesson](<https://devfeed.tech/articles/reckoning-part-2-object-lesson-26545.md>)

Original publisher: [Read original article](<https://infrequently.org/2024/08/object-lesson/>)

Author: Alex Russell

Published: 2024-08-13T00:00:00Z

Content type: article

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>), [Web](<https://devfeed.tech/topics/web.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [california](<https://devfeed.tech/tags/california.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [code](<https://devfeed.tech/tags/code.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [contentful](<https://devfeed.tech/tags/contentful.md>), [core-web-vitals](<https://devfeed.tech/tags/core-web-vitals.md>), [devices](<https://devfeed.tech/tags/devices.md>), [food](<https://devfeed.tech/tags/food.md>), [interactive](<https://devfeed.tech/tags/interactive.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [performance](<https://devfeed.tech/tags/performance.md>), [posts](<https://devfeed.tech/tags/posts.md>), [public-sector](<https://devfeed.tech/tags/public-sector.md>), [real-world](<https://devfeed.tech/tags/real-world.md>), [series](<https://devfeed.tech/tags/series.md>), [snap](<https://devfeed.tech/tags/snap.md>), [trace](<https://devfeed.tech/tags/trace.md>), [us](<https://devfeed.tech/tags/us.md>), [users](<https://devfeed.tech/tags/users.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The excerpt reports that Code for America's getcalfresh.org lets users begin interacting before BenefitsCal finishes its first of three loading screens. It attributes BenefitsCal's poor experience to a 25 MB JavaScript payload loaded before any content appears, much of it unused on the home page, and to server configuration problems that compound the wait. The excerpt says getcalfresh.org uses a simpler, progressively enhanced, HTML-first architecture for the same account and benefits signup process, drives nearly half of California benefits signups per CalSAWS, and performs substantially better in the comparison. It also cautions that BenefitsCal's multiple loading screens can mislead Chrome's Largest Contentful Paint heuristic, so public Core Web Vitals may understate the real-world delay.

### Source excerpt

Other posts in the series: Reckoning: Part 1 -- The Landscape Reckoning: Part 3 -- Caprock Reckoning: Part 4 -- The Way Out Contents The Golden Wait The Truth Is In The Trace Zip It Near Peers Blimey JavaScript Masshattery Maryland Enters The Chat Chattanooga Chug Chug SNAP? In Jersey? Fuhgeddaboudit Hoosier Hospitality Deep Breaths The Golden Wait BenefitsCal is the state of California's recently developed portal for families that need to access SNAP benefits (née "food stamps"):1 BenefitsCal loading on a low-end device over a 9Mbps link with 170ms RTT latency via WebPageTest.org Code for America's getcalfresh.org performs substantially the same function, providing a cleaner, faster, and easier-to-use alternative to California county and state benefits applications systems: getcalfresh.org loading under the same conditions The like-for-like, same-state comparison getcalfresh.org provides is unique. Few public sector services in the US have competing interfaces, and only Code for America was motivated to build one for SNAP applications. getcalfresh.org finishes in 1/3 the time, becoming interactive not long after the BenefitsCal loading screen appears. WebPageTest.org timelines document a painful progression. Users can begin to interact with getcalfresh.org before the first (of three) BenefitsCal loading screens finish (scroll right to advance): & & Google's Core Web Vitals data backs up test bench assessments. Real-world users are having a challenging time accessing the site: BenefitsCal is a poor experience on real phones. But wait! There's more. It's even worse than it looks. The multi-loading-screen structure of BenefitsCal fakes out Chrome's heuristic for when to record Largest Contentful Paint. On low-end devices, BenefitsCal appears to almost load at the 22 second mark, only to put up a second loading screen shortly after. Because this takes so long, Chromium's heuristics for Largest Contentful Paint are thrown off, incorrectly reporting the end of the first loa

[Next page](<https://devfeed.tech/sources/alex-russell.md?cursor=WyIyMDI0LTA4LTEzVDAwOjAwOjAwKzAwOjAwIiwgIjMzOTM1MmUyLWU5ZTMtNDI4My05Njk1LTc4NzNkYmRjNzcwZiJd>)