Boris Kaul

It is also possible to implement `hashCode` and `operator==` in your entity, and use it as a key for vdom node.

The whole point of vdom is to easily manage stateful trees, otherwise it is just a terrible "performance optimization". Just imagine simple user list, and now you want to render...

Without keys you just rerender the whole real DOM from scratch when something is changed. It is the easiest way to think about it, because algorithm for implicit keys is...

It is actually a good idea, it is possible only as a static method, or using some annotation that will mark one of the properties as a key, because we...

I've tried similar approach in [liquid](https://github.com/localvoid/liquid) library, and I think that it was a mistake. For example, creating functions with names like `a`, or `i` just feels like I am...

Variables like `i` are commonly used in for-loops. `area`, `map`, `input`, etc are likely to be used as Component properties, or vars inside of `updateView` method. So, now everyone starts...

If you prefer this way to create virtual nodes, you can always create additional library that will have such helpers. I really don't like this approach, especially with getters. And...

Another difference that comes to my mind is that ivi uses direct calls to DOM methods to avoid megamorphic callsites [1][2] , but vanillajs implementation doesn't have megamorphic callsites, so...

Trying to find any differences in the DOM output. Maybe because `` elements has classes `lbl` and `remove`, but there aren't any css rules for this classes, so it is...

> I'll commit that too I think that this classes (`lbl`, `remove`) are used in vanilla because of event delegation. Originally, all implementations like React, etc didn't have this classes:...