Caridy Patiño

@katyo I'm not proposing any changes on the modules, `h`, `toVNode` or `thunk` at the moment, only few more APIs on `htmldomapi` to support fragments, and few changes in the...

@JSteunou yes, but I will recommend to be caution because that doesn't work with shadow DOM and some custom events, and probably mislead users. The alternative is always to have...

> The idea is legit, could every module have an init which accepts the domapi? That will make the module code stateful, which is not desirable. Additionally, making that domapi...

I don't really see too much of a gain here, it will not simplify `snabbdom`, it will not improve the ergonomics of the API, it will not improve the perf...

@staltz IMO `patch()` is not in the critical path? `patchVnode` is definitely important since it is called multiple times during the diffing algo, while `patch()` is only call once for...

you can solve this today by doing: ```js patch(toVNode(document.getElementById('container')), vtree) ``` no changes needed.

@bloodyKnuckles yes, that's part of #359 (which is implemented by #362) in which such ambiguity is not longer a problem since you're forced to always use `toVNode`.

@bloodyKnuckles you don't need any of these to just skip the element. You can create a simple vnode without data and/or children, and a unique key, and snabbdom will not...

> @caridy how does the key in the vnode correspond with the DOM element to be skipped? this is not really required! you can probably go without the key if...

@bloodyKnuckles maybe I don't understand that. Snabbdom is very simple, you have two children collection, the oldVnode.children and the newVnode.children, and you have to compare them, independently of what is...