Yes! h always returns a memory address to a VNode. In C++ this address is reinterpreted in a VNode, that contains others VNode as children. If you decide to manually manage the memory, you can implement some interesting mechanism to diff vnodes and create vdom trees.
To do this, I have to develop some APIs that allows you, for example, to replace a children with another and so on. This is certainly on the roadmap!
Thank you for your answer. I just want to add a little thing to the first point.
> Why the single quotes around function names?
In this case I use quotes to prevent name mangling. I have to be sure that the uglify plugin in webpack does not mangle the names of that object because I'll call it from C++ in this way:
The only reason to put the license in every file is if the "project" is really a loose collection of independent files, or if you stay up at night fearing a madman on the loose randomly downloads and reuses single files from your projects.
MIT specifically calls out that the notice must be included in copies of "substantial portions" of the software which makes no sense if the entirety of the notice is already part of every file.
> The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
