A look at the rise of React, an open-source JavaScript library for building user interfaces, which is led by a small team of full-time developers at Facebook
On the social, cultural, and technological impacts of the increasingly ubiquitous frontend framework.
Context & Ripple Effects
This profile lands mid-arc in a decade-long story: Facebook had already extended React beyond the browser with React Native for native iOS apps and rebuilt its core for speed in the React Fiber reimplementation. The through-line is that a library maintained by a small full-time team inside one company became default frontend infrastructure — a dependency the wider industry kept adopting faster than Facebook could govern it.
First-order effects
- Every team building on React inherits a roadmap set by a handful of Facebook/Meta employees, making their priorities — performance work like Fiber, mobile parity via React Native — de facto standards for the frontend ecosystem.
Second-order effects
- Community trust became the binding constraint: after open-source backlash over licensing, Facebook moved React to the MIT license, trading legal leverage for continued adoption by companies that would later sit on its governing board.
Third-order effects
- The endpoint visible in the corpus is structural: stewardship moves out of the vendor entirely, with the React Foundation at the Linux Foundation giving Amazon, Microsoft, Meta, and Expo shared control — the standard resolution when single-company open source becomes critical infrastructure.
The trend: Corporate-originated open-source projects are migrating from vendor control to neutral foundations once their ecosystems grow larger than the company that created them.