One issue I have with the article is that it reads like React was the first framework to bring componentized and encapsulated UI elements to the party, when in fact that was the norm for frameworks before Backbone and Angular. Specifically Dojo and YUI where heavily focused on components.
Our shops avoided Angular altogether due to the complexity with larger apps, and used few other frameworks and libraries instead.
Trying various real world React examples frankly seems to involve more code, and the learning curve for React+Flux/redux/etc is really not trivial for a lot of people.
Overall, my recommendation is to use the simplest approach that works, and start adding libraries/frameworks only when they add clear value.
On the plus side: - It makes applications significantly more declarative, which is a readability win for me - It simplifies applications with rich history awareness. - It is fairly easy to reason about (particularly as compared with Angular) and debug. I find it conceptually more straightforward than backbone as well.
React pushed more on components acting as pure functions of state to DOM, but that style was not totally uncommon before React. Even in many old MVC frameworks, the best practices would lead to "stateless" views, and often controllers that act as pure functions for ease of testing.
I would say popularizing those functional principles, even if React actually implements them somewhat loosely, is Reacts best contribution. Eventually I think those principles will make their way into Web Components implementations, and we'll have interoperable components with React-like internals interoperating with any other off-the-shelf web component.
The DOM isn't (that) slow; it's all the crap we do to it that makes it slow.
React's strongest selling point is its ergonomics: It frees the developer from having to write huge swaths of code that they otherwise would be with most previous libraries/frameworks.
It achieves that with its immediate mode rendering: you no longer have to reason about how to transition the DOM from one state to another (in nearly all cases).