Every non-trivial (>10k lines) Cocoa/iOS/Android application I've ever seen or worked on has re-implemented at least some parts of React's data flow model. It's surprising to me that the author glosses over handling lists, which is a huge challenge with this approach, and one that forces you to do some React-like stuff (UITableView cell recycling identifiers!) even if you don't want to.
However, there are definitely some problem domains that don't map very well to the React model. Real time games, for example, have very different requirements.