Mutable Web Like Node Tree , aka DOM

[barelyhuman]

Make sure that the updates to the DOM are only reflected on the child that has changed instead of rendering the entire app from root again.

This is caused because the entire dom tree is built again instead of just the node that has changed.

Options

• This can be achieved by using a concept like cyclejs where the re-rendered child node is sent in a steamed fashion, and instead of the current React tree creation which just constructs React.createElement we could create class components that do this.

[barelyhuman]

A recommendation by @developit,

• inline undom and add an update functionality directly on the Nodes and use them to create the render tree instead of react

this might also involve writing an abstraction of react native's SDK to act as the component render call.

This solution can then lead to not needing react in the deps altogether if done properly.

Though I don't know enough of the internals to be sure if this will keep the "register new components" logic that the renderer supports right now, will learn more once I this is implemented