Hacker News Reader

React `createElement` is not the same as `document.createElement`. The exact behavior of react elements still has a lot of complexity IMO. A react element is not analogous to a DOM element. It's more like a factory for creating a DOM elements. You can put the same react element in a document twice, no problem. That doesn't work for DOM elements. That's just the tip of the iceberg.

View on HN

This is because you define what you want the components result to be. But not how to do it.

The return of a component render is a description of more work to do. When that’s done is up to reacts scheduler.

Once react has rendered a tree it then commits it to the dom.

Manipulating dom elements at runtime is imperative work. Doing it server side you get the same declarative capability as react, but no runtime behaviour.

React elements not being 1:1 with the DOM is what enables us to also target native, tuis, and so on.

Reply on news.ycombinator.com