Boris Kaul

uix is just a view library like React, and I am not sure that I will be able to write guides, docs that will explain how to build ui applications(core...

@krausest I am not sure about other libraries, but I think that the only difference (DOM operations) between ivi and vanillajs is that when table is cleared, it removes rows...

This is the edge case when it will use more DOM ops than it is necessary because of prefix/suffix optimization, I've added a note about this case in ivi sources:...

@PutziSan I guess you maybe interested to look at [ivi](https://github.com/localvoid/ivi) for some inspiration in your proposal, I've implemented `() => (props) => vdom` API on the next day after React...

> But I never had the case with my projects that I needed a `prop`` to initialize and then later worked with it in the actual UI. Easily solvable by...

> providing compile options that do both is even better than having only one choice. Why should I choose a subset of an awful DOM API as a universal retained...

> Actually they're still usable Usable doesn't mean that they will be useful. If I am going to target different platform, I am going to use different architecture/algorithms/etc and I...

> And just lacking innerHTML means "awful" is really entertaining to be heard. I've never said that "lacking innerHTML means awful" or anything like that.

> even if this can be accomodated, how will it behave for deeper/more complex data structures? Since they are using a lossy reactive graph (signals lose all information about data...

> but this requirement for deep diffing doesn't exist inside the framework itself, which is the crucial point here. It doesn't exist when working with vanilla DOM API either. Voby/Solid...