Skip to content
FrontDepth, Home

Static HTML and server rendering → Flux and Redux

1991 – today · 2014 – today

Older era
Newer era
Compare

What changed

Where the state lives

Static HTML and server rendering

On the server: the todo list is server data; the current filter is in the URL and in hidden form fields.

Flux and Redux

In one Redux store: { todos, filter }, built by two reducers joined with combineReducers. Only the half-typed text stays in the input, read through a ref.

How the page is rendered

Static HTML and server rendering

The server writes the whole page as an HTML string for every request; the browser only displays it.

Flux and Redux

React still renders the components; connect renders TodoApp again when the props it maps from the store change.

What happens on a change

Static HTML and server rendering

Every action is a request: a form POST or a link GET, answered by a complete new page.

Flux and Redux

A handler calls a prop like onToggle(id), which dispatches toggleTodo(id); the reducer returns a new state and the store notifies its subscribers.

How the code is organised

Static HTML and server rendering

One server program that routes requests and renders pages. No JavaScript is needed in the browser.

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.

  1. Static HTML and server rendering→Dynamic HTML and the browser wars

    Every change, even ticking one checkbox, is a round trip to the server and a new page: the screen flashes, the scroll position and anything half-typed are lost, and the user waits for the network each time. Pages could not react to the user on their own. JavaScript (1995) and Dynamic HTML let the page change itself in the browser.

  2. 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.

  3. 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 with attachEvent instead of addEventListener, 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.

  4. 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.

  5. 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.

  6. 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 a setTimeout callback 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.

  7. 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, setState calls 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.

Static HTML and server rendering
Flux and Redux

Static HTML and server rendering

plain browser APIs, no library

/server.js · 83 lines

JavaScript
// Static HTML era: the server builds every page; the browser shows it and sends forms back.
// In the 1990s this was a CGI script (often Perl, later PHP); here it is JavaScript.

// The "database" lives on the server, so the list survives every page load.
const todos = [
  { id: 1, title: "Read the docs", done: true },
  { id: 2, title: "Write the app", done: false },
];
let nextId = 3;

const FILTERS = { all: "All", active: "Active", done: "Done" };

// Text typed by users must be escaped before it goes into the HTML.
function escapeHtml(text) {
  return String(text)
    .replace(/&/g, "&amp;")
    .replace(/</g, "&lt;")
    .replace(/>/g, "&gt;")
    .replace(/"/g, "&quot;");
}

function renderPage(filter) {
  const shown = todos.filter((t) => filter === "all" || (filter === "done") === t.done);
  const left = todos.filter((t) => !t.done).length;

  // Every todo gets its own little form: toggling it is a POST to the server.
  const items = shown
    .map(
      (t) => `
        <li${t.done ? ' class="done"' : ""}>
          <form method="post" action="/todos/${t.id}/toggle">
            <input type="hidden" name="filter" value="${filter}">
            <button type="submit" data-toggle>${t.done ? "Undo" : "Done"}</button>
          </form>
          <span class="title">${escapeHtml(t.title)}</span>
        </li>`,
    )
    .join("");

  // Filters are plain links: choosing one loads a new page.
  const links = Object.entries(FILTERS)
    .map(
      ([name, label]) =>
        `<a href="/?filter=${name}" data-filter="${name}"${name === filter ? ' class="selected"' : ""}>${label}</a>`,
    )
    .join(" ");

  return `
    <main class="todo-app">
      <h1>Todos</h1>
      <form id="todo-form" method="post" action="/todos">
        <input type="hidden" name="filter" value="${filter}">
        <input id="new-todo" name="title" placeholder="What needs doing?" autocomplete="off" aria-label="New todo">
        <button id="add" type="submit">Add</button>
      </form>
      <ul id="todo-list">${items}
      </ul>
      <div class="footer">
        <span id="todo-count">${left} left</span>
        <div class="filters">${links}</div>
      </div>
    </main>`;
}

// One request in, one whole page out. The answer to a POST is the new page itself.
export function handle({ method, path, query, form }) {
  const asked = form?.filter ?? query.filter;
  const filter = Object.hasOwn(FILTERS, asked ?? "") ? asked : "all";

  if (method === "POST" && path === "/todos") {
    const title = (form.title ?? "").trim();
    if (title) todos.push({ id: nextId++, title, done: false });
  }

  const toggle = path.match(/^\/todos\/(\d+)\/toggle$/);
  if (method === "POST" && toggle) {
    const todo = todos.find((t) => t.id === Number(toggle[1]));
    if (todo) todo.done = !todo.done;
  }

  if (path === "/" || method === "POST") return { status: 200, body: renderPage(filter) };
  return { status: 404, body: "<h1>Not found</h1>" };
}

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

JSX
// 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);