Modern Frontend Complexity: essential or accidental?

A short history

It has been reported that the web started out painfully simple — static .html files, a sprinkle of CSS, and server-side templates that looked almost identical to what the browser actually rendered. Then JavaScript arrived, forms got smarter, and AJAX opened the door to partial updates without full-page reloads. From there, the Single Page App era kicked in: Backbone, Knockout, AngularJS and cousins changed the game. Nostalgia alert: a lot of developers still miss the days when the source code was the runtime. Who wouldn’t? Less moving parts, fewer surprises.

The gap that grew — and why it matters

Today, it has been reported that most apps are built with React, Vue, Angular or Svelte and live behind toolchains like Vite or Webpack. That’s where the real shift happens: source formats (TypeScript, TSX, JSX) must be transpiled, bundled and otherwise massaged before a browser can run them. TypeScript to JavaScript, TSX to JSX, JSX to JavaScript — and then tens or hundreds of modules get stitched into bundles for performance. The browser plays the end role, not the place where humans write code; that distance creates complexity by design.

Is this complexity essential or accidental? Allegedly both. The modern stack buys developer ergonomics, reusable components, and performance optimizations that were hard to imagine in the old world. But it also piles cognitive overhead, build-time mysteries, and fragile tooling into every project. Developers love the power; they gripe about the price. We’ve traded the simple, auditable pipeline of early web days for a richer — and messier — ecosystem. Worth it? Depends who you ask.

Sources: binaryigor.com, Lobsters