OvermindDL1

> I think key should be used for reordering to make it match with pretty much every other framework (the benchmark is even called "keyed" benchmark!). id (or a better...

> Yeah that makes sense. One key (pun!) difference is that HTML's id values are unique to the page but key values are meant to be unique among siblings only....

> I'm not sure what `uniq` does. `uniq` will recreate the node is the `uniq` value changes, but it otherwise diff's as normal. Thus if you want to make sure...

Entirely planned someday, but bucklescript keeps changing so it needs to be designed carefully to handle that... ^.^;

Code splitting it usually more for client work rather than server work, but yeah that would potentially help reduce initial page load time when having a multitude of views. Unsure...

I tend to follow the styles of the webcomponents spec for my work, so I inherently get code splitting already, plus progressive enhancement (a thing I think most sites are...

> Webcomponents use shadow DOM, which is not possible to express as HTML, so instead they render HTML and on client they erase HTML and create shadow dom. The shadow...

> I understand this as they hide everything in shadow dom. It all depends on use case. In general WebComponents using shadow DOM were originally designed to just let people...

Doesn't Elm cause a runtime error as well in the same case? I know passing functions via messages is not 'safe' in the Elm style (nor storing them in the...

> It uses immutability, effects and exhaustive check to do the trick. It fails at the 'will not see runtime errors in practice' quite a bit. There are a *LOT*...