ivi VS voby

ivi, Preact, and more

And the answer was: it depends. The Virtual DOM library I tested, ivi, had no issues handling more components. But Lit and Svelte were dramatically worse. They scaled back to almost React levels of performance as I broke them down to more components. All their non-VDOM performance benefits basically disappeared.

Some things are just inherently complex. Look at virtual dom reconciliation algorithm, for example. Others simply don't benefit from overly aggressive pursuit of "improvements". Look at database levels of normalization for another example of how one can apply theoretical "best practices" to the wazoo and completely lose sight of pragmatism.

My plan was to read Voby's code. It's similar to Solid but less code to read.

voby (Fabio Spampinato) The Million.js "template" concept is derived from Voby's template() API.

By and large having no VDOM frees you from having to structure things in an unergonomic way, for performance or otherwise, whatever limitations Svelte and Solid have in this regard are self-inflicted. For example my framework allows you to destructure props just fine, still no VDOM (https://github.com/vobyjs/voby).

Hello 👋, my name is Fabio and in the process of trying to deeply understand the awesome Solid framework I ended up writing my own standalone reactivity library, Oby, and a Solid-like reactive framework on top of it, Voby.