Dynamic HTML and the browser wars → Flux and Redux
1995 – today · 2014 – today
What changed
- Where the state lives
Dynamic HTML and the browser wars
In the page: a JavaScript array and a filter variable. Nothing is saved; a reload starts again from the code.
Flux and Redux
In one Redux store:
{ todos, filter }, built by two reducers joined withcombineReducers. Only the half-typed text stays in the input, read through a ref.- How the page is rendered
Dynamic HTML and the browser wars
render()builds the whole list as one HTML string and swaps it in withinnerHTML.Flux and Redux
React still renders the components;
connectrendersTodoAppagain when the props it maps from the store change.- What happens on a change
Dynamic HTML and the browser wars
Handler attributes (
onsubmit,onclick) call global functions that change the array and callrender().Flux and Redux
A handler calls a prop like
onToggle(id), which dispatchestoggleTodo(id); the reducer returns a new state and the store notifies its subscribers.- How the code is organised
Dynamic HTML and the browser wars
One script of global functions, wired to the page by attributes in the HTML. No server is involved.
Flux and Redux
Action types and creators, reducers, the store setup and a connected function component, each in its own file.
Why it changed
What hurt in each era along the way, and the era that came next.
Dynamic HTML and the browser wars→AJAX
The page could change itself, but it could not exchange data with the server without leaving: loading fresh data or saving a change still meant a form submission or a link and a whole new page, and everything kept in variables was gone after it. On top of that, every browser needed its own branch of the code. XMLHttpRequest and the AJAX approach let a script talk to the server in the background and update only the part of the page that changed.
AJAX→jQuery
Every browser did it a little differently. Internet Explorer 5 and 6 created the object with
new ActiveXObject("Microsoft.XMLHTTP"), Internet Explorer before version 9 attached events withattachEventinstead ofaddEventListener, and each browser had its own DOM quirks, so scripts grew long and full of browser checks. Libraries like jQuery wrapped XHR, events and the DOM in one short API that worked the same in every browser.jQuery→MVC in the browser (Backbone)
When the data lives only in the DOM, every feature reads and writes the page directly: the counter counts
<li>elements, the filter checks classes. As apps grew, handlers changing the page from many places became hard to follow ("jQuery spaghetti"), and there was no model of the data to test, save or reuse. Libraries like Backbone moved the data into models and kept the page in views.MVC in the browser (Backbone)→Two-way binding (AngularJS)
Backbone left the wiring to you. Every view subscribed to its models by hand, chose what to redraw and read form fields back itself, so much of the code only connected data to the DOM. A view thrown away without
remove()stayed subscribed and kept reacting as a "zombie view", and re-rendering a template replaced elements, losing focus and half-typed text. AngularJS answered with two-way data binding: the HTML declares what shows what, and the framework keeps the page and the data in sync.Two-way binding (AngularJS)→React and the virtual DOM
Every binding added a watcher, and every digest checked all of them, at least twice whenever something had changed, so pages with many bindings slowed down on each click or keystroke (1.3 added one-time bindings,
::, to cut the count). Two-way bindings and watchers that change other values made it hard to see what changed what, and code outside AngularJS, like asetTimeoutcallback or a jQuery plugin, had to remember to call$scope.$apply().Angular 2 was a new framework rather than the next version: an app could not just upgrade, and the official path was to migrate it piece by piece, with both frameworks running side by side. React answered with one-way data flow: a component renders from its state, and a virtual DOM works out what to change on the page.
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.
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.
Dynamic HTML and the browser wars
plain browser APIs, no library
/src/main.js · 73 lines
// DHTML era: the page changes itself in the browser. The list is a JavaScript array, and
// render() writes it into the page as one HTML string. No server is asked.
// The state is plain variables in the page: a reload starts again from these lines.
var todos = [
{ id: 1, title: "Read the docs", done: true },
{ id: 2, title: "Write the app", done: false }
];
var nextId = 3;
var filter = "all";
var FILTERS = ["all", "active", "done"];
// The text the user typed becomes part of the HTML, so it is escaped first.
function escapeHtml(text) {
return text.replace(/&/g, "&").replace(/</g, "<").replace(/>/g, ">").replace(/"/g, """);
}
function render() {
var html = "";
var left = 0;
var i, todo;
for (i = 0; i < todos.length; i++) {
todo = todos[i];
if (!todo.done) left++;
if (filter == "all" || (filter == "done") == todo.done) {
// The handler is part of the string: onclick calls a global function with the id.
html += '<li' + (todo.done ? ' class="done"' : '') + '><label>' +
'<input type="checkbox" data-toggle onclick="toggleTodo(' + todo.id + ')"' +
(todo.done ? ' checked' : '') + '> ' +
'<span class="title">' + escapeHtml(todo.title) + '</span></label></li>';
}
}
// innerHTML throws the old items away and builds new ones, so a focused checkbox loses focus.
document.getElementById("todo-list").innerHTML = html;
document.getElementById("todo-count").innerHTML = left + " left";
for (i = 0; i < FILTERS.length; i++) {
document.getElementById("filter-" + FILTERS[i]).className = FILTERS[i] == filter ? "selected" : "";
}
}
function addTodo() {
var field = document.getElementById("new-todo");
var title = field.value.replace(/^\s+|\s+$/g, "");
if (title != "") {
todos.push({ id: nextId++, title: title, done: false });
field.value = "";
render();
}
// false cancels what the browser would do next: send the form and load a new page.
return false;
}
function toggleTodo(id) {
for (var i = 0; i < todos.length; i++) {
if (todos[i].id == id) todos[i].done = !todos[i].done;
}
render();
}
function setFilter(name) {
filter = name;
render();
}
// A <script> of the time ran in the global scope: every function above became global, and
// the onclick attributes could call it. The lab runs each file as a module with its own
// scope, so the functions the markup calls are put on window by hand.
window.addTodo = addTodo;
window.toggleTodo = toggleTodo;
window.setFilter = setFilter;
// Like a <script> at the end of <body>, this runs when the elements already exist: draw the list.
render();Flux and Redux
React 19.3.0, React DOM 19.3.0, Redux 5.0.1, React Redux 9.3.1
/src/App.jsx · 91 lines
// A container component: it owns no data. connect() passes it the store's state and the actions as props.
// JSX then compiled to React.createElement, so React had to be imported; the automatic runtime used here does not need it.
import React from "react";
import { connect } from "react-redux";
import { addTodo, toggleTodo, setFilter } from "./actions.js";
const FILTERS = { all: "All", active: "Active", done: "Done" };
// A plain function of props, as in the Redux docs of the time: the typed text is read from
// the input through a ref, so the component needs no state of its own.
function TodoApp({ todos, left, filter, onAdd, onToggle, onFilter }) {
let input;
function handleSubmit(event) {
event.preventDefault();
const title = input.value.trim();
if (!title) return;
onAdd(title);
input.value = "";
}
return (
<main className="todo-app">
<h1>Todos</h1>
<form id="todo-form" onSubmit={handleSubmit}>
<input
id="new-todo"
ref={(node) => {
input = node;
}}
placeholder="What needs doing?"
autoComplete="off"
aria-label="New todo"
/>
<button id="add" type="submit">
Add
</button>
</form>
<ul id="todo-list">
{todos.map((todo) => (
<li key={todo.id} className={todo.done ? "done" : undefined}>
<label>
<input
type="checkbox"
data-toggle
checked={todo.done}
onChange={() => onToggle(todo.id)}
/>{" "}
<span className="title">{todo.title}</span>
</label>
</li>
))}
</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={() => onFilter(name)}
>
{FILTERS[name]}
</button>
))}
</div>
</div>
</main>
);
}
// Picks what the component reads from the state. Derived values are computed, not stored.
const mapStateToProps = (state) => ({
todos: state.todos.filter((t) => state.filter === "all" || (state.filter === "done") === t.done),
left: state.todos.filter((t) => !t.done).length,
filter: state.filter,
});
// The component never changes data itself: its callbacks dispatch actions to the store.
const mapDispatchToProps = (dispatch) => ({
onAdd: (title) => dispatch(addTodo(title)),
onToggle: (id) => dispatch(toggleTodo(id)),
onFilter: (name) => dispatch(setFilter(name)),
});
// connect() subscribes to the store, runs mapStateToProps when the state changes and renders
// TodoApp again when the result differs. @deprecated since React-Redux 9.3 (hooks are
// recommended), it still works the same and prints nothing (legacy_connect is the same).
export default connect(mapStateToProps, mapDispatchToProps)(TodoApp);