React and the virtual DOM → Component frameworks (Vue, Angular, Svelte)
2013 – today · 2014 – today
What changed
- Where the state lives
React and the virtual DOM
In
this.stateof the topAppclass: the todos, the filter and the typed text, changed only throughthis.setState.Component frameworks (Vue, Angular, Svelte)
In the component's
data(): plain objects and arrays that Vue makes reactive.shownandleftarecomputed, cached until the data they read changes.- How the page is rendered
React and the virtual DOM
render()returns the whole UI as React elements on every change; React compares them with the previous ones and patches only the DOM that differs.Component frameworks (Vue, Angular, Svelte)
Vue compiles the HTML template (written in the page here) into a render function. When data it read changes, the component re-renders and Vue patches only what differs.
- What happens on a change
React and the virtual DOM
A bound handler calls
this.setState; React merges the change into the state and callsrender()again.Component frameworks (Vue, Angular, Svelte)
Methods and
v-modelchange the data directly (this.todos.push,todo.done); Vue buffers the DOM update until the next tick, a microtask.- How the code is organised
React and the virtual DOM
A class component that owns the state and a small function component that gets props: data goes down as props, changes come back up through callbacks.
Component frameworks (Vue, Angular, Svelte)
One component object of options (
data,computed,methods) plus its template. Larger apps nest such components into a tree.
Why it changed
What hurt in each era along the way, and the era that came next.
React and the virtual DOM→Flux and Redux
State that several components need has to live in their closest common parent and travel down as props through every component in between, even those that only pass it on, while callbacks travel down the same way to change it. In a large app,
setStatecalls in many components, triggered by clicks, server responses and timers, all changed what the screen showed, so it was hard to follow why it looked the way it did. Flux and Redux moved the shared state out of the components into a store that changes only through actions.Flux and Redux→Component frameworks (Vue, Angular, Svelte)
Every small feature needed the same pieces in several files: an action type constant, an action creator, a case in a reducer, and
mapStateToProps/mapDispatchToPropsto connect a component, plus objects copied by hand so that nothing was mutated. Setting up a store with middleware and the DevTools took more code still. Redux itself later answered with Redux Toolkit; component frameworks like Vue, Angular and Svelte offered reactive state you change directly and HTML templates that update themselves, with much less ceremony.
The same app, side by side
The main file of each version. Both apps pass the same test: same markup, same behaviour, different ideas.
The apps run in sandboxes in your browser.
React and the virtual DOM
React 19.3.0, React DOM 19.3.0
/src/App.jsx · 98 lines
// Virtual DOM era: render() describes the whole UI from this.state, and React updates the DOM.
// JSX then compiled to React.createElement, so every file imported React; the automatic runtime used here does not need it.
import React from "react";
import TodoItem from "./TodoItem.jsx";
const FILTERS = { all: "All", active: "Active", done: "Done" };
let nextId = 3;
export default class App extends React.Component {
constructor(props) {
super(props);
// The top component owns the state; its children get pieces of it as props.
this.state = {
todos: [
{ id: 1, title: "Read the docs", done: true },
{ id: 2, title: "Write the app", done: false },
],
filter: "all",
title: "",
};
// A class method passed as a callback loses `this`, so each handler is bound once here.
this.handleChange = this.handleChange.bind(this);
this.handleSubmit = this.handleSubmit.bind(this);
this.toggle = this.toggle.bind(this);
}
handleChange(event) {
// setState merges the given keys into this.state and asks React to render again.
this.setState({ title: event.target.value });
}
handleSubmit(event) {
event.preventDefault();
const title = this.state.title.trim();
if (!title) return;
const todo = { id: nextId++, title, done: false };
// setState is a request, not an immediate change: the function form gets the latest state.
this.setState((state) => ({ todos: state.todos.concat(todo), title: "" }));
}
toggle(id) {
// Copy the todo instead of changing it. Object spread ({ ...t }) only became standard
// in ES2018, so code of the time used Object.assign.
this.setState((state) => ({
todos: state.todos.map((t) => (t.id === id ? Object.assign({}, t, { done: !t.done }) : t)),
}));
}
// React calls it again on every state change, compares the new elements with the previous ones
// (the virtual DOM) and changes only the DOM nodes that differ.
render() {
const { todos, filter, title } = this.state;
const shown = todos.filter((t) => filter === "all" || (filter === "done") === t.done);
const left = todos.filter((t) => !t.done).length;
return (
<main className="todo-app">
<h1>Todos</h1>
<form id="todo-form" onSubmit={this.handleSubmit}>
<input
id="new-todo"
value={title}
onChange={this.handleChange}
placeholder="What needs doing?"
autoComplete="off"
aria-label="New todo"
/>
<button id="add" type="submit">
Add
</button>
</form>
<ul id="todo-list">
{/* Data goes down as props; the change comes back up through onToggle. */}
{shown.map((todo) => (
<TodoItem key={todo.id} todo={todo} onToggle={this.toggle} />
))}
</ul>
<div className="footer">
<span id="todo-count">{left} left</span>
<div className="filters">
{Object.keys(FILTERS).map((name) => (
<button
key={name}
type="button"
data-filter={name}
className={filter === name ? "selected" : undefined}
onClick={() => this.setState({ filter: name })}
>
{FILTERS[name]}
</button>
))}
</div>
</div>
</main>
);
}
}Component frameworks (Vue, Angular, Svelte)
Vue 3.5.45
/src/main.js · 41 lines
// Component-framework era (Vue): the component declares its state, derived values and
// methods; the HTML template in index.html describes the page. Vue keeps the two in sync.
import { createApp } from "vue";
let nextId = 3;
createApp({
// data() returns the state. Vue makes it reactive: while rendering it records which
// properties were read, and any later change to them re-renders the component.
data() {
return {
todos: [
{ id: 1, title: "Read the docs", done: true },
{ id: 2, title: "Write the app", done: false },
],
filter: "all",
title: "",
};
},
// Computed values are cached and re-evaluated only when the data they read changes.
computed: {
shown() {
return this.todos.filter((t) => this.filter === "all" || (this.filter === "done") === t.done);
},
left() {
return this.todos.filter((t) => !t.done).length;
},
},
methods: {
addTodo() {
const title = this.title.trim();
if (!title) return;
// A plain push is enough: no new array, no setState. Vue sees the change itself.
this.todos.push({ id: nextId++, title, done: false });
this.title = "";
},
},
// There is no template option, so mount() uses the HTML inside #app as the template.
}).mount("#app");