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.