[waps]

I second this. The issue with angular is it's attempt to approach a functional paradigm in the UI : the UI fully mirrors the state of the data and vice-versa.

React, by contrast, doesn't do state change detection and instead counts on the programmer to tell it when the state's changed.

What this article is saying is that if you use the advanced hacks in angular to disable large parts of that state reflection, then angular is (almost) as fast as react. This is true, but it's very misleading : if you don't use angular the way it's designed, the way it's used in every one of their tutorials and start manually updating things ... then it's fast.

That's great, but using frameworks in a way which is working around their core design principles is going to be very unpleasant.