But that's not especially important when it comes to React in general. The important is that the "how to draw myself" (in a high level) never leaves the view, not whether the "drawing instuctions" happen inside the app (as low level draw commands) or outside (by a mechanism that handles composable values representing markup).
In both cases the view is a black box -- in that nobody else determines it's layout/style/contents. Whether somebody else or the view itself draws them might reflect a functional vs more imperative style, but it's not the key benefit of react.
In fact there are React implementations like React-Canvas that don't use the DOM/diffing mechanism at all -- they just invalidate the whole top level "viewport".
Serious question, and I'm not a Windows programmer, I might be missing something.
https://facebook.github.io/react/docs/component-api.html#for...
That's a red herring. That would be relevant if we were discussing the imperative vs functional methodology.
But what the article discusses is the similarity in the architecture of two view management systems.
And even more so, the imperative changes in the Windows scheme described are encapsulated inside the views, and the overall system is more functional that you give it credit for. But, again, I think that this is beside the point.
One is a lot easier to unit test than the other, for example.