Skip to content
FrontDepth, Home

AJAX → React and the virtual DOM

1999 – today · 2013 – today

Older era
Newer era
Compare

What changed

Where the state lives

AJAX

On the server: the list is server data; the page keeps the last copy it received, and the filter.

React and the virtual DOM

In this.state of the top App class: the todos, the filter and the typed text, changed only through this.setState.

How the page is rendered

AJAX

The server sends data (JSON), not HTML; the page builds the list items with document.createElement.

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.

What happens on a change

AJAX

Each change is a background request; its callback replaces the page's copy of the list and redraws only the list, the counter and the filter buttons.

React and the virtual DOM

A bound handler calls this.setState; React merges the change into the state and calls render() again.

How the code is organised

AJAX

A page script with a request helper and handlers attached in window.onload, talking to a server API that answers JSON.

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.

Why it changed

What hurt in each era along the way, and the era that came next.

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

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

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

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

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.

AJAX
React and the virtual DOM

AJAX

plain browser APIs, no library

/src/main.js · 97 lines

JavaScript
// AJAX era: the page talks to the server in the background with XMLHttpRequest and
// redraws only the list. The page itself is never loaded again.

// The list belongs to the server; the page keeps the last copy it received.
var todos = [];
var filter = "all";

// Every request goes the same way: open, send, then wait until readyState is 4 (done).
function request(method, url, body, callback) {
  var xhr = new XMLHttpRequest();
  // true = asynchronous: the page stays usable while the request travels.
  xhr.open(method, url, true);
  if (body) xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
  xhr.onreadystatechange = function () {
    if (xhr.readyState === 4 && xhr.status === 200) {
      callback(JSON.parse(xhr.responseText));
    }
  };
  xhr.send(body);
}

// Every answer is the whole list as JSON: keep it and redraw.
function show(list) {
  todos = list;
  render();
}

// One call per todo gives each handler its own todo. A handler created inside render()'s
// for loop would close over the loop's single var and see its value from the end of the loop.
function makeItem(todo) {
  var li = document.createElement("li");
  var label = document.createElement("label");
  var box = document.createElement("input");
  var title = document.createElement("span");
  box.type = "checkbox";
  box.checked = todo.done;
  box.setAttribute("data-toggle", "");
  box.onclick = function () {
    request("POST", "/todos/" + todo.id + "/toggle", null, show);
  };
  // A text node: what the user typed never becomes HTML.
  title.className = "title";
  title.appendChild(document.createTextNode(todo.title));
  label.appendChild(box);
  label.appendChild(document.createTextNode(" "));
  label.appendChild(title);
  li.appendChild(label);
  if (todo.done) li.className = "done";
  return li;
}

// Only the list, the counter and the filter buttons change; the rest of the page stays.
function render() {
  var list = document.getElementById("todo-list");
  var buttons = document.getElementById("filters").getElementsByTagName("button");
  var left = 0;
  var i;
  list.innerHTML = "";
  for (i = 0; i < todos.length; i++) {
    if (!todos[i].done) left++;
    if (filter === "all" || (filter === "done") === todos[i].done) {
      list.appendChild(makeItem(todos[i]));
    }
  }
  document.getElementById("todo-count").innerHTML = left + " left";
  for (i = 0; i < buttons.length; i++) {
    buttons[i].className = buttons[i].getAttribute("data-filter") === filter ? "selected" : "";
  }
}

// Handlers are attached from the script when the page has loaded, not written into the HTML.
window.onload = function () {
  var field = document.getElementById("new-todo");
  var buttons = document.getElementById("filters").getElementsByTagName("button");
  var i;

  document.getElementById("todo-form").onsubmit = function () {
    var title = field.value.replace(/^\s+|\s+$/g, "");
    if (title !== "") {
      request("POST", "/todos", "title=" + encodeURIComponent(title), show);
      field.value = "";
    }
    // false cancels the normal submission: no new page, the request runs in the background.
    return false;
  };

  for (i = 0; i < buttons.length; i++) {
    // Inside the handler, this is the button that was clicked.
    buttons[i].onclick = function () {
      filter = this.getAttribute("data-filter");
      render();
    };
  }

  // The page arrives without the list; the first request fetches it.
  request("GET", "/todos", null, show);
};

React and the virtual DOM

React 19.3.0, React DOM 19.3.0

/src/App.jsx · 98 lines

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