ivi
ivi copied to clipboard
Great project! Much better than React on design
Please consider continue develop this project.
Hope to see:
- [ ] Target Independent reconciler.
- [ ] Bridge on React to provide ivi like api.
Thanks, for the last several months I've been tinkering with some experimental algorithms that had different tradeoffs, but it seems that all this experimental solutions were worse. There are some major changes that I am planning to make in ivi, like removing textContent="" optimization. This optimization detects when all children nodes should be removed/replaced and removes all of them with one DOM operation, it has a huge impact on results in synthetic benchmarks, but in real applications I usually solve use cases that trigger big list removals by wrapping children lists in another DOM node because it also improves DOM creation performance, especially when browsers has extensions that use MutationObserver. Also, I am planning to reduce overall code complexity by removing Server-Side Rendering.
I don't like the idea of target independent reconcilers because there are a lot of target-specific optimization that won't make any sense when targeting different platforms. In my opinion it is better to maintain completely different code bases with the same APIs to target different platforms.
I don't think that is possible to create ivi API on top of React. For example, ivi synthetic events will be quite hard to implement in React.