The author understands React quite well, it's this comment that, while also understanding React, misses the author's point by insisting on the superficial differences.
>It does actually - you update the state, then React propogates the changes for you through it's props mechanism.
That it achieves something (change propagation) it doesn't mean it's the solution to that thing. There's a reason the author used the wording "doesn't solve" (instead of "doesn't handle", "doesn't allow" etc). Flux (and it's variations) is what really solves propagation in React without it becoming a tangled mess.
>Flux is not message passing
Nobody said it is.
>React components do not redraw themselves
They do, that's the whole point. React components manage, compose and return their DOM representation structure which is the HTML analogous to "drawing". return(<b>{msg}</b>) IS drawing.
The fact that they don't have low level rendering code embedded in them is just an implementation detail (because of course the DOM already exists).
>React provides the view as a function of state. Windows is nothing like that.
Only the author doesn't mention Windows, the abstract OS, he mentions a specific implementation of its UI engine that clearly provides the view as a function of state.
Similar miscomprehensions of the article drive the other objections.