Framework · 2017–now · Platform Wars
Tailwind CSS
Utility classes in markup upset purists and accelerated shipping. Design systems without meeting paralysis.
Tailwind stuck because co-located styling beats global CSS archaeology for product teams on deadlines. Purists hate class strings; metrics love shipped pages. It mutated design culture more than Bootstrap did.
Patterns
Context
Frameworks fought for the runtime
Front-end frameworks consolidated power; TypeScript became table stakes; Next and friends absorbed routing, data, and deploy gravity. Serverless and Jamstack rebranded old ideas with better CDNs, then cooled when auth and personalization refused to stay static. Blockchain-for-CRUD and big-bang rewrites collected dumb budgets. The winners were boring platforms with ecosystems — React gravity, Rust where systems care, Vite for greenfield bundling. The losers were narratives that skipped product-market fit or treated every App Router rewrite as destiny.
Compare with
Related
Framework · 2013–now
React
Components and unidirectional data. Won the front-end by being good enough and having a gravitational ecosystem.
Framework · 2011–now
Bootstrap
Opinionated CSS that made every site look like a startup for a while. Still the fastest path to a decent admin UI.
Framework · 2016–now
Svelte / SvelteKit
Compile away the framework. Less runtime theater, more shipped HTML — including this site.