Two-way binding (AngularJS) → SSR, SSG and meta-frameworks
2010 – 2021 · 2016 – today
What changed
- Where the state lives
Two-way binding (AngularJS)
On
$scope: plain objects in$scope.todos, the filter in$scope.showand the text field's value in$scope.newTitle.SSR, SSG and meta-frameworks
In the page component's
this.state, started from the props the server loaded withgetInitialProps(); a copy of those props travels with the HTML as JSON.- How the page is rendered
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.SSR, SSG and meta-frameworks
The server renders the whole page to HTML with
renderToString(); the browser hydrates it withhydrateRoot()and renders every later change itself.- What happens on a change
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.SSR, SSG and meta-frameworks
After hydration everything happens in the browser: a handler calls
this.setState()and React re-renders the page component. Nothing goes back to the server.- How the code is organised
Two-way binding (AngularJS)
A module, a controller that fills
$scope, and directives in the HTML. The controller has no DOM code.SSR, SSG and meta-frameworks
A page in
pages/written once for both sides, plus framework code: a server that renders and serializes, and a client entry that hydrates.
Why it changed
What hurt in each era along the way, and the era that came next.
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.Flux and Redux→Component frameworks (Vue, Angular, Svelte)
Every small feature needed the same pieces in several files: an action type constant, an action creator, a case in a reducer, and
mapStateToProps/mapDispatchToPropsto connect a component, plus objects copied by hand so that nothing was mutated. Setting up a store with middleware and the DevTools took more code still. Redux itself later answered with Redux Toolkit; component frameworks like Vue, Angular and Svelte offered reactive state you change directly and HTML templates that update themselves, with much less ceremony.Component frameworks (Vue, Angular, Svelte)→SSR, SSG and meta-frameworks
These apps still rendered in the browser. The server sent an almost empty page, and nothing useful appeared until the framework and the app's JavaScript had downloaded and run; crawlers and link previews that do not run JavaScript saw nothing. Routing, server rendering, code splitting and data loading were left to each team to put together. Meta-frameworks such as Next.js and Nuxt bundled those pieces around the component framework and rendered pages on the server or at build time.
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.
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>SSR, SSG and meta-frameworks
React 19.3.0, React DOM 19.3.0
/pages/index.jsx · 101 lines
// A page as Next.js apps wrote it in 2016–2018: a class component with a static data method.
// The same file runs twice: on the server (to HTML) and in the browser (hydration).
import { Component } from "react";
const FILTERS = { all: "All", active: "Active", done: "Done" };
export default class TodoPage extends Component {
// Called on the server before the first render; what it returns becomes the page's props.
// A real page would read a database or an API here.
static async getInitialProps() {
return {
todos: [
{ id: 1, title: "Read the docs", done: true },
{ id: 2, title: "Write the app", done: false },
],
};
}
constructor(props) {
super(props);
// The first state comes only from props, so the server and the browser render the same HTML.
this.state = { todos: props.todos, filter: "all", title: "" };
this.nextId = Math.max(0, ...props.todos.map((t) => t.id)) + 1;
this.handleChange = this.handleChange.bind(this);
this.handleSubmit = this.handleSubmit.bind(this);
}
handleChange(event) {
this.setState({ title: event.target.value });
}
handleSubmit(event) {
event.preventDefault();
const title = this.state.title.trim();
if (!title) return;
const todo = { id: this.nextId++, title, done: false };
this.setState((state) => ({ todos: [...state.todos, todo], title: "" }));
}
toggle(id) {
this.setState((state) => ({
todos: state.todos.map((t) => (t.id === id ? { ...t, done: !t.done } : t)),
}));
}
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">
{shown.map((todo) => (
<li key={todo.id} className={todo.done ? "done" : undefined}>
<label>
<input
type="checkbox"
data-toggle
checked={todo.done}
onChange={() => this.toggle(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.entries(FILTERS).map(([name, label]) => (
<button
key={name}
type="button"
data-filter={name}
className={filter === name ? "selected" : undefined}
onClick={() => this.setState({ filter: name })}
>
{label}
</button>
))}
</div>
</div>
</main>
);
}
}