713: The CSS OG Eric Meyer. 1994 CSS, JS in Fridges, Tailwind, and Web Standards

Episode Summary

Executive Summary: Eric Meyer traces his career from early web days to modern CSS stewardship, explaining how specs, test suites, and cross-browser collaboration made CSS far more interoperable. The conversation covers CSS history, the role of working groups and vendors, native features evolving from preprocessors, and concerns about browser funding, Firefox’s future, and where web tech now runs beyond the browser.

Main Topics: Eric Meyer’s path into the web and CSS: Meyer recounts his early work at Case Western, discovering Mosaic, becoming a webmaster, and transitioning into CSS advocacy, writing, and testing. CSS test suites and standards maturation: He explains how his CSS1 test pages evolved into an official W3C test suite and how web platform tests now drive implementation consistency across browsers. How CSS features ship today: The discussion highlights iterative implementation through flags, working group debate, and tests, using Grid, Flexbox, container queries, and :has() as examples. Preprocessors influencing native CSS: Meyer discusses how Sass/LESS inspired native CSS features such as nesting and color manipulation, while noting the contentious debate over syntax choices. Tailwind, inline styling, and maintainability: He gives a skeptical but pragmatic view of utility-first/inlined styling, arguing that whether a tool is good depends on workflow, maintainability, and fit for the author. Web technology everywhere: Meyer describes web engines and web tech powering devices like game consoles, cars, elevators, set-top boxes, spacecraft, and even a space telescope. Browser funding and Firefox’s future: The conversation turns to the economics of browsers, with Meyer warning that much of the ecosystem is subsidized by Google search revenue and that Firefox’s long-term survival is uncertain without it.

Key Arguments: CSS interoperability improved because specs became more explicit and test-driven, reducing ambiguity that once led browsers to implement features differently. Modern browser features often emerge through a churn of prototype, test, implement, and working-group resolution before wide release. Preprocessors served as real-world proof of demand for features like nesting and color functions, making native equivalents easier to justify. Utility-first and inline-style approaches can be productive for some developers, but Meyer argues the cascade and external stylesheets remain more maintainable for many use cases. The browser ecosystem depends heavily on a few companies’ incentives and funding, especially Google’s search revenue, which supports browser development indirectly. Web technology is now an embedded platform used far beyond traditional browsing, making standards work more important and more widespread than ever.

Data Points: Year of first HTML document: 1993/1994 (Meyer says 30 years ago from the recording date) - He marked up his first HTML document on December 5, roughly two years before JavaScript’s birthday mentioned in the conversation. JavaScript birthday referenced: 28 years old - Scott/Wes mention December 4 as JavaScript’s 28th birthday during the discussion. CSS1 scope: ~70 properties - Meyer describes the original CSS1 browser support table as covering about 70 properties. CSS: The Definitive Guide page count: 1,100+ pages in 5th edition - He compares the first edition to the recent fifth edition, emphasizing how much CSS has grown. First edition page count: ~400 pages - The first edition of CSS: The Definitive Guide was much shorter than the current version. Web Platform Tests size: Over 1 million tests - He notes the modern test suite is extremely large across all web platform features. Interop origin: 5 areas in the first year - He explains that Interop began with only five implementation focus areas, then expanded greatly. Interop 2024 proposals: Over 100 proposed; cut to 71 - He says more than 100 ideas were proposed, then reduced to just over 70 because some lacked specs or working groups. Netscape Navigator price: $40 - He recalls early Netscape Navigator being sold as boxed software for forty dollars. CSS color work: 40% darker / 20% lighter examples - He uses relative color adjustments as examples of desired native CSS color-mixing behavior.

Pivotal Quotes: "the cascade is actually your friend and not your enemy" — Eric Meyer: His critique of utility-heavy and fully inlined styling approaches, arguing that external styles and the cascade are valuable. "It’s kind of a miracle that anything is able, like that complex is able to get added to the platform and all this stuff just works." — Wes Bos: Reflecting on the complexity of adding advanced features like container queries and the stability now achieved. "The entire web technology advancement is built on Google ad revenue, all of it." — Eric Meyer: His blunt warning about the economic dependence of browsers and web standards implementation on Google’s search business.

Implications: Listeners get a clear view of why the modern web is more stable: standards now rely on testing, iteration, and cross-vendor coordination. The episode also underscores real risks around browser funding, plus the growing reach of web tech into embedded systems and nontraditional devices.