Instead, the modern compiler is used at build time to generate what looks like a change detection function and a DOM update function per component.
These functions will detect changes and update the DOM in an optimal way without any DOM diffing.
However, because Javascript objects by default are mutable, after each browser event Angular in its default change detection mode has to check all the template expressions in all the components for changes, because the browser event might have potentially triggered changes in any part of the component tree.
If we want to introduce some restrictions and make the data immutable, then we can check only the components that received new data by using OnPush change detection, and even bypass whole branches of the component tree.
This is the current state of things, for the near future Angular is having it's internals rebuilt in a project called Ivy.
One of the main goals of Icy is to implement a principle called component locality.
Ivy aims at getting to a point where if we change only one component, we only have to recompile that component and not the whole application.
I think the article puts the focus on the wrong thing. The current change detection and DOM update mechanisms made available by modern frameworks virtual DOM or not are more than fast enough for users to notice, including on mobile and once the application is started.
What we need is ways to ship less code to the browser, because that extra payload makes a huge difference in application startup time.