Skip to content
FrontDepth, Home

Two-way binding (AngularJS) → Server components and islands

2010 – 2021 · 2020 – today

Older era
Newer era
Compare

What changed

Where the state lives

Two-way binding (AngularJS)

On $scope: plain objects in $scope.todos, the filter in $scope.show and the text field's value in $scope.newTitle.

Server components and islands

In the island's useState, started from the props the server serialized next to it. The static parts have no state at all.

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.

Server components and islands

The server renders the whole page to HTML; only the island's element is hydrated with hydrateRoot(). React never touches the static HTML.

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-model also writes from the field back to the scope.

Server components and islands

Inside the island a setter re-renders TodoApp and React updates the DOM that differs; the rest of the page never changes.

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.

Server components and islands

Server-only components that never reach the browser, around client islands that each have their own root, script and props.

Why it changed

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

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

  2. 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, setState calls 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.

  3. 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 / mapDispatchToProps to 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.

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

  5. SSR, SSG and meta-frameworks→Hooks

    Pages now arrived rendered, but the components were still classes: one feature's logic was spread over componentDidMount, componentDidUpdate and componentWillUnmount, sharing stateful logic needed higher-order components or render props, and every handler had to be bound to this (see the constructor). Hooks (React 16.8, 2019) gave function components state and effects that can be shared as custom hooks.

    Hydration had its own cost: the browser downloads and runs the code of the whole page, even of parts that never change, and the data travels twice, as HTML and as JSON. Islands and server components later went after that.

  6. Hooks→Server components and islands

    Everything still ran in the browser: the page arrived empty, every component's JavaScript had to download, run and render before anything useful appeared, and server rendering hydrated the whole page even where nothing was interactive. Effects with dependency arrays and stale closures became a common source of bugs. Islands and React Server Components moved the non-interactive parts back to the server.

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)
Server components and islands

Two-way binding (AngularJS)

AngularJS 1.8.3

/index.html · 35 lines

HTML
<!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>

Server components and islands

React 19.3.0, React DOM 19.3.0

/server.jsx · 48 lines

JSX
// Islands era: the server renders the whole page to HTML, and only the islands get JavaScript.
// An islands framework such as Astro does this for you: you only mark what is interactive.
import { renderToStaticMarkup, renderToString } from "react-dom/server";
import TodoApp from "./islands/TodoApp.jsx";

// The "database" lives on the server.
const todos = [
  { id: 1, title: "Read the docs", done: true },
  { id: 2, title: "Write the app", done: false },
];

// A server-only component: it runs here and leaves plain HTML behind. It ships NO JavaScript:
// this file is never sent to the browser, and nothing hydrates its HTML.
function Intro() {
  return (
    <>
      <h1>Todos</h1>
      <p>This heading and note are plain HTML with no JavaScript. Everything below them is an island.</p>
    </>
  );
}

// "<" is escaped so that a todo titled "</script>" cannot end the script element early.
function serialize(props) {
  return JSON.stringify(props).replace(/</g, "\\u003c");
}

export async function handle({ method, path }) {
  if (method !== "GET" || path !== "/") return { status: 404, body: "<h1>Not found</h1>" };
  const props = { initialTodos: todos };

  // Static part: HTML only, without the markers hydration needs. No JavaScript.
  const intro = renderToStaticMarkup(<Intro />);

  // The island: HTML that hydrateRoot can attach to, with its props as JSON right next to it.
  const island = renderToString(<TodoApp {...props} />);

  return {
    status: 200,
    body: `
    <main class="todo-app">
      ${intro}
      <div id="todo-island">${island}</div>
      <script id="todo-island-props" type="application/json">${serialize(props)}</script>
    </main>
    <script src="/client.jsx"></script>`,
  };
}