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