PROVIDER Β· the de facto standard for component-based frontend development

React

React is Meta's component-based UI library rendering from JSX and state, whose richest ecosystem, largest job market, and Next.js and React Native extensions make it the frontend de facto standard.

Programming Languages & Frameworks United States 2026.11.16
Programming Languages & Frameworks United States the de facto standard for component-based frontend development
4.8pts

Pros

4 items
A clear component model where JSX keeps markup and logic together
The richest ecosystem with mature libraries for nearly every need
Largest job demand with the deepest talent pool and learning material
React Native and Next.js extend skills to mobile and full stack

Cons

4 items
The core is only a UI library with routing and data assembled separately
Too many state options cause architectural confusion when chosen poorly
Manual memoisation is required with a steep learning curve for performance work
Paradigm shifts such as Server Components demand continuous learning

Product Information

react
Category Programming Languages & Frameworks
Company React
Service Region United States
Official Website https://react.dev/
Recommendation Score 4.8 pts
Published 2026-11-16

Detailed Notes

Overview

React was open sourced by Facebook, now Meta, in 2013 as the flagship component-based UI library, describing interfaces in JSX, rendering from state, and diffing with a virtual DOM, with Hooks introduced in 2019 giving function components full state capability.

For Programming Languages & Frameworks work the value is ecosystem and talent scale, since component libraries, state management, routing, forms, and charts all offer several mature options, job demand is the largest among frontend frameworks making hiring easiest, and React Native extends the model to mobile while Next.js covers SSR and full stack.

Note the costs, because the core is only a UI library leaving routing and data fetching to assemble, numerous state options from Context to Redux, Zustand, and TanStack Query cause confusion when chosen poorly, and render performance depends on manual memoisation with frequent re-renders a common issue.

Core Strengths

  • A clear component model where JSX keeps markup and logic together
  • The richest ecosystem with mature libraries for nearly every need
  • Largest job demand with the deepest talent pool and learning material
  • React Native and Next.js extend skills to mobile and full stack

Product Ecosystem

Core capabilities

Components and props, Hooks such as useState, useEffect, and useMemo, plus Context and Suspense.

Ecosystem choices

React Router or Next.js for routing, Zustand or Redux for state, and TanStack Query for data.

Tooling

Vite or Next.js scaffolding with TypeScript, ESLint, and React Testing Library.

Drawbacks

  • The core is only a UI library with routing and data assembled separately
  • Too many state options cause architectural confusion when chosen poorly
  • Manual memoisation is required with a steep learning curve for performance work
  • Paradigm shifts such as Server Components demand continuous learning

Use Cases

  • Medium and large frontend apps (β˜…β˜…β˜…β˜…β˜…) - Most complete ecosystem
  • Hiring and team collaboration (β˜…β˜…β˜…β˜…β˜…) - Largest talent pool
  • Cross-platform mobile (β˜…β˜…β˜…β˜…) - React Native
  • Very light static pages (β˜…β˜…β˜…) - Vanilla or Astro is leaner

Pricing

Plan Price Scope
React and React DOM $0 MIT licensed, free
Ecosystem libraries $0 Open source and free
Enterprise support Optional Via consultancies or the Meta ecosystem

The framework and ecosystem are free with cost in engineering governance across build tooling, monitoring, testing, and performance work, while the lowest learning and hiring cost explains its wide adoption.

FAQ

  • Is React a framework or a library? Officially a UI library, with routing, data fetching, and full stack provided by frameworks like Next.js.

  • React or Vue? React has more jobs and a larger ecosystem while Vue onboards more smoothly with better Chinese docs, and concepts transfer cheaply.

  • Are class components still needed? No, Hooks cover all capability and class components appear only in legacy code.

Code Examples

Function component with hooks

import { useEffect, useState } from 'react';

export default function Plans() {
  const [plans, setPlans] = useState([]);

  useEffect(() => {
    fetch('/api/plans').then((r) => r.json()).then(setPlans);
  }, []);

  return <ul>{plans.map((p) => <li key={p.id}>{p.name}</li>)}</ul>;
}

Keys must be stable and unique since index keys corrupt state when items reorder.

Server components

async function Plans() {
  const plans = await db.plan.findMany({ where: { price: { lt: 80 } } });
  return <ul>{plans.map((p) => <li key={p.id}>{p.name}</li>)}</ul>;
}

Community & Resources

Communities and official channels

Learning resources and tools

Visit React Website β†’ https://react.dev/
Visit Website β†—