Echoes
Echoes
Cost Structures Dressed as Architectural Truth
In 2005, a widely circulated essay told web developers to forget everything they knew about the server. Fifteen years later, the React team told them to forget everything they knew about the client. Both announcements carried the quiet confidence of people who had found the permanent answer.
The web has been arguing about where to assemble a page for thirty years. Each resolution arrived with conviction. Each eventually reversed. The current hybrid approach looks different, looks like hard-won synthesis. So did the last two, from the inside. And in every era, the cost structures doing the actual pushing went mostly undiscussed.
Cost Structures Dressed as Architectural Truth
In 2005, a widely circulated essay told web developers to forget everything they knew about the server. Fifteen years later, the React team told them to forget everything they knew about the client. Both announcements carried the quiet confidence of people who had found the permanent answer.
The web has been arguing about where to assemble a page for thirty years. Each resolution arrived with conviction. Each eventually reversed. The current hybrid approach looks different, looks like hard-won synthesis. So did the last two, from the inside. And in every era, the cost structures doing the actual pushing went mostly undiscussed.
The Ten-Day Ratchet
In May 1995, Brendan Eich was hired to put Scheme in the browser. Netscape's marketing team had other plans: make it look like Java, don't let it compete with Java, and ship it yesterday. Ten days later, the prototype was done. The design was, in Eich's words, "frozen by necessity."
That frost never thawed. The language now runs on 98.8% of websites. Every architectural swing since, from server-rendered pages to SPAs to React Server Components, plays out on top of it. TypeScript, used by 78% of professional developers in 2026, exists to catch what ten days couldn't finish. It compiles down to JavaScript. The ratchet clicked in 1995. Everything since is sediment.
One-Way Turns
Dead Engines Stay Dead
Plenty of things in technology swing back and forth. Browser engine diversity only decreases. Five engines existed in 2013. Three remain today. The two that died are staying dead, and the conditions that killed them have only intensified since. Mozilla recently advocated for engine diversity, but the mechanism underneath their warning only clicks forward. The sole independent engine left is financially dependent on the company whose dominance it exists to counterbalance.
What the Pendulum Leaves Behind
Where rendering happens on the web does swing back and forth. Server to client, client back to server. Each swing deposits frameworks, build tools, and mental models that never fully clear away. jQuery shipped in 2006 and still runs on nearly 78% of top websites. Eleven build tools arrived in a single decade. The pendulum implies a clean return. Underneath, the weight only accumulates.
Pendulums and Ratchets
