The Web’s Complexity Problem Is Real—and Reversible

Christian Heilmann’s talk at Typo3 Developer Days cuts straight to a frustration many of us feel: the more elaborate web development becomes, the harder it is to get started. His comparison of two hypothetical stacks says it all.

Once, a website was simply index.html. Today, the journey looks something like this:

  • Find the right editor with the right extensions
  • Config a terminal with the perfect font and dotfiles
  • Install framework flügelhorn.js with bundler wolperdinger.io
  • Run packagestuff –g install and watch the warnings pile up
  • Break something, then sudo your way through it
  • Ignore the ever-growing node_modules folder
  • Learn the abstraction windfarm.css that promises productivity
  • Replace HTML with the templating language funsocks
  • Finally see a “hello world” example—an hour later

It’s a deliberately glib list, but the underlying point holds. Ten years ago, I was wrestling with Grunt and convinced I’d never master it. Eventually I did, but the tools have only piled up since. Even experienced developers feel it. As Pixel Envy puts it:

This world is unfortunately becoming lost or, at least, degraded — not because it is no longer possible to view the source of a webpage, but because that source is often inscrutable, even on simple webpages.

— Pixel Envy “A View Source Web”

Resilience Is Already There—We Just Ignore It

Heilmann’s core reminder is that the web’s foundation isn’t fragile. It’s the opposite. Browsers update continuously, standards move faster than ever, and most of us don’t need to build software that scales to infinity—that’s a niche requirement, not a default one.

The headline that captures his point best:

The web is built on resilient technologies – we just don’t use them

The Pendulum Can Swing Back

This echoes something Molly White wrote earlier this year: the old, view-source-friendly web hasn’t vanished. Nothing prevents us from returning to simpler patterns while keeping the genuinely useful developments of the last decade.

The thing is: none of this is gone. Nothing about the web has changed that prevents us from going back. If anything, it’s become a lot easier. We can return. Better, yet: we can restore the things we loved about the old web while incorporating the wonderful things that have emerged since, developing even better things as we go forward, and leaving behind some things from the early web days we all too often forget when we put on our rose-colored glasses.

We can return. That’s not nostalgia; it’s a practical choice about how much abstraction a project really needs. The tools aren’t the problem—the reflex to reach for all of them at once is. The question is whether we’re willing to make that call.