Skip to content
FrontDepth, Home

Static HTML and server rendering → jQuery

1991 – today · 2006 – 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.

jQuery

In the DOM: a todo is done when its <li> has the class done, and the counter is found by counting elements.

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.

jQuery

The server sends the first HTML. New items are built with $("<li>") and appended.

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.

jQuery

Each handler changes the elements it knows about, then refresh() fixes the counter and the filter.

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.

jQuery

One script of event handlers. A delegated handler on #todo-list also covers items added later.

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.

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
jQuery

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>" };
}

jQuery

jQuery 4.0.0

/src/main.js · 52 lines

JavaScript
// jQuery era: the page itself is the state. Handlers read the DOM, change it, recount.
import $ from "jquery";

// $(fn) waits until the document is ready, like $(document).ready(fn).
$(function () {
  let filter = "all";

  // Brings the counter, the visible items and the filter buttons in line with the DOM.
  function refresh() {
    const left = $("#todo-list li").not(".done").length;
    $("#todo-count").text(left + " left");

    $("#todo-list li").each(function () {
      const done = $(this).hasClass("done");
      $(this).toggle(filter === "all" || (filter === "done") === done);
    });

    $("[data-filter]").removeClass("selected");
    $('[data-filter="' + filter + '"]').addClass("selected");
  }

  $("#todo-form").on("submit", function (event) {
    event.preventDefault();
    const title = String($("#new-todo").val()).trim();
    if (!title) return;

    // Build the new <li> the same way the server wrote the first ones.
    const $item = $("<li>").append(
      $("<label>").append(
        $('<input type="checkbox" data-toggle>'),
        " ",
        $('<span class="title">').text(title),
      ),
    );
    $("#todo-list").append($item);
    $("#new-todo").val("");
    refresh();
  });

  // One delegated handler on the list also covers the items added later.
  $("#todo-list").on("change", "[data-toggle]", function () {
    $(this).closest("li").toggleClass("done", this.checked);
    refresh();
  });

  $(".filters").on("click", "[data-filter]", function () {
    filter = $(this).data("filter");
    refresh();
  });

  refresh();
});