The Gardener's First Staked and Unstaked Saplings

There is a quiet tension in every garden, a debate as old as the soil itself. Do you stake the young sapling, guiding its growth with external support, or do you let it find its own way, trusting its inner strength to weather the winds? This is not merely a question of horticulture; it is the precise dilemma we face when building for the modern web, particularly in the realm of our foundational frameworks.

On one side of the plot, we have the staked sapling: the monolithic framework. This is the meticulously planned support system, the Angular or Ember of the world. It is planted with intention, its growth path pre-determined by a rigid trellis of conventions, built-in tooling, and a prescribed way of doing things. The initial yield is impressive—a strong, upright structure that grows quickly and uniformly. There is immense comfort in this. The gardener knows exactly what to expect, and the sapling is protected from many of the early, chaotic elements.

Yet, the stake itself can become a constraint. As the tree matures, that initial support can chafe, leaving marks on the bark. The very structure designed to empower growth can, over seasons, inhibit the natural, organic spread of branches. The framework’s entire ecosystem must be carried along, a weight that remains even when certain parts are no longer needed. The initial speed of growth can be offset by the eventual burden of its own infrastructure.

Across the path grows the unstaked sapling: the lean collection of micro-libraries. This is the Svelte or Preact approach, or a hand-rolled composition of focused tools. Here, the gardener provides rich soil and ample sunlight—a robust browser and native web APIs—but then steps back. The sapling is forced to develop a strong, resilient trunk on its own. It must grapple with the wind early on, and in doing so, it builds a dense, internal strength that needs no external prop.

The result is a different kind of beauty. It is wilder, more adaptable, and astonishingly lightweight. It uses only what it needs, shedding leaves in winter without losing its core form. Its performance is innate, not engineered. But this approach demands a more knowledgeable gardener, one who can identify every pest and nutrient deficiency without a manual. The initial growth can seem slower, more deliberate, as the roots must dig deeper before a visible spurt appears.

One approach offers the safety of a guided path and the risk of eventual constraint. The other offers the freedom of adaptive strength and the peril of the unguided. One is a curated garden; the other is a resilient part of the forest itself. The true craft lies not in declaring a winner, but in understanding the nature of the plant you wish to grow and the ecosystem you are cultivating. The best gardens, like the best web experiences, often contain a thoughtful mixture of both.

Notes & further reading

A few pages I came back to while writing this: