Introduction
The only constant on the web is change. As soon as you master one approach, a new paradigm emerges. This cycle mirrors parenthood: just when you think you have a handle on feedings and diapers, you’re thrown into potty training and preschool. For those of us who have spent decades designing and developing for the web, we’ve witnessed this rhythmic wax and wane repeatedly—ideas, techniques, and technologies rise and fall, reshaping our craft each time.
The Wild West of the Early Web
I built my first website in the mid-1990s. Back then, web design was a free-for-all with few rules. Need a layout beyond a single column? You reached for HTML tables, often stuffing empty cells with single-pixel spacer GIFs to create whitespace. Text styling required nested <font> tags—each change of size or color meant another layer of markup. Our typeface choices were laughably slim: Arial, Courier, or Times New Roman. When Verdana and Georgia appeared in 1996, we celebrated because our options had nearly doubled.
Color was equally constrained: only the 216 “web safe” colors were reliable across platforms. Interactions like contact forms or guestbooks relied on CGI scripts (mostly Perl). To achieve any distinctive look, you stacked hack upon hack. Interactivity was largely confined to individual pages, never woven throughout a site.
The Birth of Web Standards
At the turn of the millennium, the cycle shifted. Crufty code—table layouts, font tags, spacer GIFs—began to wane as web standards waxed. CSS gained traction among browser makers and designers. This transformation didn’t happen overnight; it required tireless advocacy from the W3C, browser vendors, and evangelists like the Web Standards Project. Landmark resources such as A List Apart and Jeffrey Zeldman’s book Designing with Web Standards taught developers why standards mattered, how to implement them, and how to sell them to stakeholders.
Progressive enhancement emerged as a key approach: content should be available to all browsers, with advanced enhancements for capable ones. Meanwhile, the CSS Zen Garden demonstrated CSS’s power when paired with semantic HTML. Server-side languages like PHP, Java, and .NET replaced Perl, and the cgi-bin directory faded into history. JavaScript began its ascent as a serious tool, though early browser wars and fragmentation slowed adoption.
Modern Cycles: Responsive, Frameworks, and Beyond
The rhythm continued. Mobile devices exploded, and responsive web design—championed by Ethan Marcotte—made fluid layouts and media queries standard practice. CSS preprocessors like Sass and Less brought variables and mixins, while JavaScript frameworks (React, Vue, Angular) redefined how we build interactive interfaces. Single-page applications (SPAs) waxed, then waned as developers rediscovered simpler server-rendered patterns with tools like Next.js and Nuxt.
CSS-in-JS rose and fell; utility-first frameworks like Tailwind CSS gained momentum. The Jamstack architecture promised pre-built static sites with dynamic APIs, only to be challenged by server-side rendering and edge computing. Each new idea promised to solve the last one’s problems—until its own shortcomings emerged.
Lessons from the Cycle
Recognizing this pattern helps us stay adaptable. The web’s history teaches us that no technique is permanent. What we learn today may be obsolete tomorrow, but the core principles—accessibility, performance, usability—remain. Internal anchor links within this article (like the early web or web standards) mirror how hyperlinks have always connected knowledge.
The Constant: People and Purpose
Beneath all the technology, the web’s purpose endures: connecting people to information and each other. As we navigate the next wave—AI, Web Components, Edge Computing—we should remember that change isn’t something to fear but to embrace. The wax and wane continues, and that’s precisely what makes this field endlessly fascinating.
— Adapted from the original “The Wax and the Wane of the Web”