Tailwind's Rise as the Pragmatic Middle Ground
What you'll learn: Why Tailwind emerged as the dominant styling solution when runtime CSS-in-JS fell out of favor.
The Perfect Storm
When Server Components broke runtime CSS-in-JS libraries (styled-components, Emotion), the React ecosystem faced a crisis. Developers needed something that worked everywhere—client, server, RSC—without runtime overhead. Zero-runtime solutions like vanilla-extract offered type safety but added complexity. Plain CSS Modules felt too verbose for rapid development.
Tailwind walked into this chaos as the practical answer.
Why Tailwind Won
No runtime at all. Tailwind generates static CSS at build time. It works identically in SPAs, SSR apps, and Server Components without special configuration.
Fast to write, fast to run. Utility classes let you style components inline without leaving your JSX. No context switching between files. The generated CSS is highly cacheable and minified.
Flexible enough for real apps. Unlike rigid component libraries, Tailwind lets you customize everything through config files. Need brand colors? Add them. Need custom spacing? Done. You keep full control while moving fast.
Works with existing tools. Tailwind plays nicely with CSS Modules, CSS variables, and even CSS-in-JS for edge cases. It doesn't demand you rewrite everything.
The Pragmatic Compromise
Tailwind isn't perfect—verbose class strings can get unwieldy, and you lose some design token type safety. But it solved the ecosystem's immediate pain: a styling approach that works everywhere, ships zero runtime JavaScript, and doesn't slow down development.
It's not the most elegant solution, but it's the one that got teams shipping.
Key Takeaway: Tailwind became the default React styling choice because it combined zero-runtime performance with developer ergonomics when runtime CSS-in-JS became problematic with Server Components.