Status

AI-generated draft. Will unsloppify soon!

A strange fact: a thing can be better in the ways that matter most, and still be terrible at becoming the default.

  • Permaculture is better for soil, water, biodiversity, and long-term food security. But we practice monoculture on 80% of the world’s arable land.
  • Walkable neighborhoods are healthier, cheaper, and overwhelmingly preferred; yet most cities can’t convert because the infrastructure is already built wrong.
  • Open protocols gave us email and the web; closed platforms captured both.

Why? And what would it actually take for the better version to win?

Why beautiful things lose

It’s tempting to think that if something is genuinely better, it should just win. But “better” assumes a single scoreboard, and there isn’t one. Every environment runs its own contest — selecting for what’s cheap to adopt here, easy to finance there, fast to deploy somewhere else. A thing tuned to win the contest that matters most can be hopeless at the contest that decides what actually gets built.

Ecologists have a frame for what happens when different strategies compete in the same environment:

  • r-selected species — bacteria, dandelions, weeds — reproduce fast, colonize aggressively, and die easily.
  • K-selected species — elephants, old-growth trees, whales — grow slowly, invest heavily, and are resilient but terrible at colonizing.

They’ve since refined this into messier life-history theory, but the core split survives: some strategies are built to colonize, others to endure, and almost nothing does both well.

After Mount St. Helens erupted in 1980, the first colonizers were wind-dispersed lupines and spiders ballooning on silk threads. Within 5 years, grasses. Within 20, shrubs. The full forest recovery will take 200+ years.

Weeds are not failed trees; trees are not successful weeds. They solve different problems at different stages.

The ugly-but-scalable thing is solving the colonization problem. The beautiful thing solves the maturity problem. The tragedy is when the colonizer prevents the mature system from ever arriving.

It shows up in different costumes — a deliberate tradeoff here, distribution lock-in there, institutional failure, financing pressure — but underneath it’s always the same shape: the thing that colonizes is not the thing that’s best, and the two rarely coincide.

  • Ted Nelson’s Xanadu promised two-way links, built-in attribution, version history, and micropayments — in a design dating back to 1960. The Web shipped in 1991 with one-way links that break and no rights management. Nelson:

    • “HTML is precisely what we were trying to PREVENT.”

    • But Berners-Lee had already built two-way links in his earlier system ENQUIRE (1980) — he knew exactly what he was giving up. He later called one-way links:

    • “the principle compromise made in the W3 architecture, which then, by allowing references to be made without consultation with the destination, allowed the scalability which the later growth of the web exploited.”

    • Nelson met him around 1989 and said:

    • “he’d done this very simple thing, and it sounded too trivial to me… and the next thing I knew suddenly the thing had caught on.”

  • JavaScript was created in 10 days in 1995, with type coercion bugs that can never be fixed (typeof null === "object" is a day-one error). It won because it shipped in Netscape Navigator at 80% market share — the only scripting language in the browser.

  • Python has the GIL, a 12-year migration from 2 to 3, and is 10-100x slower than compiled languages. It won because universities made it the default teaching language, which fed a generation of developers into the data science ecosystem (NumPy, pandas, PyTorch — all C/Fortran under the hood).

  • Better-designed alternatives to both exist. They lost to the thing that got there first — which is the whole point.

  • Xerox PARC built the GUI, the mouse, Smalltalk, ethernet, and laser printing by 1973. Xerox — one of the largest corporations in the world — couldn’t scale any of it. They shipped the Star at 75,000 — and it went nowhere. Steve Jobs visited in 1979, saw the GUI, and shipped the Macintosh five years later at $2,495. A company a fraction of Xerox’s size took PARC’s beautiful ideas and actually got them into millions of people’s hands. Having the beautiful thing and having a scaling strategy for it are completely different capabilities.

  • OpenAI was founded in 2015 as a nonprofit with fiduciary duty to humanity. By late 2025 it had completed its restructuring into a for-profit corporation valued at roughly half a trillion dollars, because the nonprofit form could not generate the capital needed to compete. The mission statement changed six times in nine years of IRS filings — the latest version finally dropped the word “safely.”

Once in a while it goes the other way — and that case is the most instructive one in the list:

  • Before Stripe, accepting a credit card online meant weeks of merchant accounts, payment gateways, PCI compliance, and banking relationships. Stripe reduced it to — famously — seven lines of code. The complexity didn’t disappear; Stripe absorbed it on behalf of developers, handling the banks, the fraud detection, the regulatory maze, so the interface stayed simple. It didn’t make the colonization problem go away — it ate it. Patrick Collison:
    • “More of Stripe’s success than one would think is downstream of the fact that people like beautiful things because a beautiful thing tells you the person who made it really cared.”

The common thread: whatever wins is better fitted to the selection pressures of the current environment, whether that means being simpler to deploy, cheaper to adopt, or easier to finance.

Succession, not teleportation

So the beautiful thing and the ugly thing are adapted to different environments. But even when the beautiful thing is viable, it often can’t appear in its mature form on day one — it has to be grown through stages.

You cannot deploy a forest.

First come the pioneer species. Then grasses, shrubs, nurse trees, fungal networks, and only much later the dense interdependent thing people actually want when they say “forest”.

A lot of beautiful systems fail because they’re asked to appear in their mature form, all at once, inside an environment that can’t yet support them. (Out of Control is the long version of this: the grown beats the made, but the grown can’t be commanded into being — only cultivated.)

Walkable cities are a good example. Everyone loves them after they already exist, but they are not just an architectural style — they depend on land use, finance, transit, political coalitions, zoning, norms, and path dependence. Amsterdam was car-dominated until the Netherlands lost 3,300 people to traffic in a single year — 1971, around 500 of them children — and the Stop de Kindermoord (“stop the child murder”) protests occupied accident blackspots and closed streets so children could play. Most cities can’t convert because the infrastructure is already built wrong, and retrofitting costs orders of magnitude more than building correctly the first time.

The same is true of open protocols and permaculture — each depends on a dense web of preconditions (clients, norms, adoption thresholds, local knowledge, long feedback loops) that can only accumulate over time.

Many beautiful things are climax communities — and climax communities, by definition, can’t be exported.

Chinese mapping apps are a striking example. They can show you:

  • live red-light countdowns
  • real-time bus tracking
  • shade-percentage routing for pedestrians
  • shortcuts through parking garages

They are so far ahead of Google Maps that using them feels like time travel. But they can’t expand outside China, because their quality comes from an ecosystem — a fiercely competitive domestic mapping industry, a massive user base generating real-time data, and the Beidou positioning system, which matches GPS globally and beats it over the Asia-Pacific. The app is a product; the quality is an ecology. You can export the app, but the ecology has to grow where it is. (James C. Scott’s Seeing Like a State is relevant here — standardization strips away exactly the kind of local, context-sensitive knowledge that makes these systems work.)

Bret Victor’s Dynamicland is the Western mirror of the same problem. It’s the most compelling vision of what computing could be — spatial, communal, physical, humane — and it has been one building in Oakland for years. Not because nobody wants it, but because it is an ecology: the room is the product. You can’t ship a room.

So this is an ecology problem

Put the two halves together — different environments select for different things, and beautiful things can’t teleport into their mature form — and all these failures start to look like one failure. The winner rarely just wins. It reshapes the landscape behind it so nothing better can take root. US commodity-crop subsidies alone ran $9.3 billion in 2024, locking in the monocultures and making transition nearly impossible. Platforms don’t just beat the open web; they kill the habit of it. The colonizer doesn’t occupy the niche, it poisons it for whatever might have come next.

Which is also why you can’t just rip the colonizer out. It’s a fence: ugly, in the way, and standing there because it solved a real problem — the colonization problem — that the beautiful alternative is still pretending doesn’t exist (Chesterson’s Fence). Tear it out without replacing the function it served and you get nothing, faster.

And even the apparent successes are suspect. Often the surface pattern spreads while the generative logic dies — the form travels, the life doesn’t, which is closer to embalming than scaling. So the real test of a beautiful thing was never “is it better.” It’s whether it can travel: survive contact with incentives that would cheapen it, grow without skipping the stages it needs, regenerate in the hands of strangers without losing its essence. The more a thing leans on local knowledge, dense relationships, patience, and integrity, the more easily that test breaks it.

What it would take

Here’s the part the makers of beautiful things least want to hear: being right is not the finish line. Just because you’re right doesn’t mean you’ll survive — solve for distribution and endurance. Most beautiful things die because their makers treat scaling as beneath them — a compromise, a sellout, someone else’s job. It isn’t. It’s part of the design.

The rare winners knew this. Stripe didn’t wait for developers to learn the banking system; it swallowed the banking system and handed back seven lines. Jobs didn’t lecture anyone on the elegance of the GUI; he put it in a $2,495 box and shipped it, while Xerox — orders of magnitude larger — couldn’t move the same ideas past a five-figure price tag. They treated the colonization problem as their problem: they built the ugly, scalable carrier and the beautiful payload, and refused to ship one without the other.

But craft isn’t always enough, and pretending it is has its own naivety. Sometimes the environment has to move first. Amsterdam didn’t out-design the car — 3,300 people died in a single year and the grief changed what the streets were allowed to select for. You can build the most beautiful thing in the world and still be waiting on a disturbance that never comes. The most you can do is already exist when it does, in some early, spreadable form, ready for the opening. (Why Greatness Cannot Be Planned: you don’t reach the climax by marching at it; you accumulate stepping stones until the next one is in reach.)

So the answer to the question I opened with is two-sided, and I only half have it. The maker’s half I’m fairly sure of: build distribution into the thing, eat the colonization problem yourself, and stop mistaking being right for being safe. The other half is the one I keep circling — what would an ecology that selects for maturity actually look like? What has to be true about incentives, institutions, norms, and ownership for a better pattern to spread without being hollowed into a surface? I don’t have that half yet. But I’m increasingly sure it’s one of the hidden subproblems under most of the problems I care about, and under a lot of my Open Loops. Make the beautiful thing — then do the unbeautiful work of making sure it survives long enough to become the default. The alternative is the world we mostly have: colonized, again and again, by whatever was merely good enough to get there first.