React

React is like a stage crew that resets only the parts of a set that actually changed between scenes, rather than rebuilding the whole stage from scratch every time the curtain rises. First released by engineers at Meta in 2013, it's a JavaScript library for building user interfaces, structured around breaking an interface into small, self-contained components — a button, a navigation bar, a data table — each responsible for its own logic and appearance, and each reusable wherever it's needed.

React sits at the frontend layer of a project — it handles what users see and interact with, not the server logic or database behind it. Because it only updates the parts of a page that actually change, rather than re-rendering everything, it holds up well in interfaces with frequent data updates or heavy user interaction. In practice, it's commonly paired with a framework like Next.js, which adds routing, server-side rendering, and deployment optimisations on top of React's component model — a combination well suited to applications that need both a rich interface and strong performance.

The trade-offs are worth naming honestly. Because React is a library rather than a full framework, teams have to make explicit choices about routing, state management, and data fetching — decisions that more opinionated frameworks bundle together by default. For smaller teams or tight timelines, that overhead is real, and React's mental model around when and how components re-render takes some time to learn. That said, its ecosystem is enormous: with one of the largest developer communities in the industry behind it, practical solutions to almost any problem are well documented and battle-tested, which keeps React a dependable choice for interactive, data-driven applications.