Two-way binding (AngularJS) → Component frameworks (Vue, Angular, Svelte)
2010 – 2021 · 2014 – 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.Component frameworks (Vue, Angular, Svelte)
In the component's
data(): plain objects and arrays that Vue makes reactive.shownandleftarecomputed, cached until the data they read changes.- 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.Component frameworks (Vue, Angular, Svelte)
Vue compiles the HTML template (written in the page here) into a render function. When data it read changes, the component re-renders and Vue patches only what differs.
- 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.Component frameworks (Vue, Angular, Svelte)
Methods and
v-modelchange the data directly (this.todos.push,todo.done); Vue buffers the DOM update until the next tick, a microtask.- 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.Component frameworks (Vue, Angular, Svelte)
One component object of options (
data,computed,methods) plus its template. Larger apps nest such components into a tree.
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.
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>Component frameworks (Vue, Angular, Svelte)
Vue 3.5.45
/src/main.js · 41 lines
// Component-framework era (Vue): the component declares its state, derived values and
// methods; the HTML template in index.html describes the page. Vue keeps the two in sync.
import { createApp } from "vue";
let nextId = 3;
createApp({
// data() returns the state. Vue makes it reactive: while rendering it records which
// properties were read, and any later change to them re-renders the component.
data() {
return {
todos: [
{ id: 1, title: "Read the docs", done: true },
{ id: 2, title: "Write the app", done: false },
],
filter: "all",
title: "",
};
},
// Computed values are cached and re-evaluated only when the data they read changes.
computed: {
shown() {
return this.todos.filter((t) => this.filter === "all" || (this.filter === "done") === t.done);
},
left() {
return this.todos.filter((t) => !t.done).length;
},
},
methods: {
addTodo() {
const title = this.title.trim();
if (!title) return;
// A plain push is enough: no new array, no setState. Vue sees the change itself.
this.todos.push({ id: nextId++, title, done: false });
this.title = "";
},
},
// There is no template option, so mount() uses the HTML inside #app as the template.
}).mount("#app");