AJAX → Two-way binding (AngularJS)
1999 – today · 2010 – 2021
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.
Two-way binding (AngularJS)
On
$scope: plain objects in$scope.todos, the filter in$scope.showand the text field's value in$scope.newTitle.- How the page is rendered
AJAX
The server sends data (JSON), not HTML; the page builds the list items with
document.createElement.Two-way binding (AngularJS)
The HTML is the template: AngularJS compiles the
ng-*attributes and{{ }}once, then each binding updates its own piece of the DOM.- 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.
Two-way binding (AngularJS)
Directives run handlers inside
$apply; the digest evaluates every watcher again and changes the DOM where a value differs.ng-modelalso writes from the field back to the scope.- 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.Two-way binding (AngularJS)
A module, a controller that fills
$scope, and directives in the HTML. The controller has no DOM code.
Why it changed
What hurt in each era along the way, and the era that came next.
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.
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
plain browser APIs, no library
/src/main.js · 97 lines
// 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);
};Two-way binding (AngularJS)
AngularJS 1.8.3
/index.html · 35 lines
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Todos · AngularJS</title>
<link rel="stylesheet" href="/styles.css" />
</head>
<body>
<!-- The page is the template: ng-* attributes and {{ }} bind it to TodoCtrl's $scope. -->
<main class="todo-app" ng-controller="TodoCtrl">
<h1>Todos</h1>
<!-- A form without an action: AngularJS stops the real submit and calls add(). -->
<form id="todo-form" ng-submit="add()">
<!-- Two-way: typing writes $scope.newTitle, and setting newTitle changes the field. -->
<input id="new-todo" ng-model="newTitle" placeholder="What needs doing?" autocomplete="off" aria-label="New todo" />
<button id="add" type="submit">Add</button>
</form>
<ul id="todo-list">
<!-- ng-repeat gives every <li> a child scope holding its todo. ng-model="todo.done" writes -->
<!-- straight into that object, so the controller's list sees the change. -->
<li ng-repeat="todo in todos | filter:matches" ng-class="{done: todo.done}">
<label><input type="checkbox" data-toggle ng-model="todo.done" /> <span class="title">{{todo.title}}</span></label>
</li>
</ul>
<div class="footer">
<span id="todo-count">{{remaining()}} left</span>
<div class="filters">
<button type="button" data-filter="all" ng-class="{selected: show == 'all'}" ng-click="show = 'all'">All</button>
<button type="button" data-filter="active" ng-class="{selected: show == 'active'}" ng-click="show = 'active'">Active</button>
<button type="button" data-filter="done" ng-class="{selected: show == 'done'}" ng-click="show = 'done'">Done</button>
</div>
</div>
</main>
</body>
</html>