The problem
Backbone left the wiring to the developer: each view subscribed to its models, chose what to redraw and read form fields back by hand. Much of an app's code was this glue between data and DOM, and one forgotten listener left part of the page out of date.
The idea
AngularJS extends HTML with directives. ng-model binds a field to a property of the scope in both directions, ng-repeat stamps out a copy of the element for each item (here through the filter filter), ng-class sets classes from an expression, and ng-click and ng-submit call functions on the scope. The controller only puts plain data and functions on $scope; it never touches the DOM.
Every binding is a watcher. After an event, AngularJS runs a digest: it evaluates every watcher again, updates the DOM where a value changed and repeats until nothing changes (at most 10 rounds, then it stops with an error). This is dirty checking: the data is plain objects, with no set() and no events.
What hurt next
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.
How close this is to the original
Runs AngularJS 1.8.3 (April 2022), the last release. Code of 2012–2014 looked much like this and put the data on $scope, as here: the controller as syntax only arrived in 1.1.5 (May 2013). The 1.0 docs wrote controllers as global functions (function PhoneListCtrl($scope)) with ng-app on <html>; 1.3 stopped looking up controllers on window and 1.7 removed the option, so the demo registers the controller on a module. It starts the app with angular.bootstrap() instead of ng-app because the lab puts index.html into the page after angular.js has loaded.