Framework · 2013–now · Cloud Scale
React
Components and unidirectional data. Won the front-end by being good enough and having a gravitational ecosystem.
React stuck because component mental models match product teams and hiring markets at scale. Virtual DOM was a means; ecosystem and Facebook backing were the engine. It will fade eventually — everything does — but not before your next job posting.
Patterns
Context
Split everything, then pay for the glue
Hyperscale patterns escaped the companies that needed them. Containers unified packaging; Kubernetes became the cloud OS; microservices and NoSQL were sold as defaults. Mobile-first stuck because screens changed. Cargo-cult distributed systems stuck around as invoices. The durable move was packaging and ops maturity — not rewriting every app into a mesh.
Compare with
Related
Framework · 2010–2021
AngularJS (1.x)
Two-way binding magic that became a migration tax. Angular 2+ was a rewrite; the 1.x apps lingered for years.
Framework · 2014–now
Vue
Progressive framework with a friendlier learning curve. Steady share without the cult volume.
Practice · 2014–now
SPA for Every Page
Client-side apps as the only architecture. Great for apps; absurd for brochures.
$ Marketing sites and docs portals shipped multi-megabyte JS bundles for content that wanted HTML. SEO and performance teams spent years unwinding "modern" defaults.
Framework · 2015–now
React Native
React components on native views. Share logic with web until platform differences ruin your sprint.