dom-expressions VS voby

I wonder how it compares to https://github.com/ryansolid/dom-expressions/tree/main/packa...

The template core, which is in https://github.com/ryansolid/dom-expressions/tree/main/packages/dom-expressions This template core manages the DOM and SSR-related APIs that is usually hidden from the user. This core is also "cloned" into the SolidJS repo via Rollup.

Revised my comment. However, I'm required to use Babel for: https://github.com/ryansolid/dom-expressions/tree/main/packages/babel-plugin-jsx-dom-expressions and a couple other small plugins.

Solid's transform seems fairly time consuming and difficult to maintain to me, though maybe it isn't, I'm not familiar with that code or with writing Babel transforms in general, you decide.

vuerx-jsx is using Vue's reactivity system (@vue/reactivity) with Solid's DOM renderer. Both offer blazingly fast performance, (much) faster than their original usage.

Solid is great, you can also use it with hyper dom expressions: https://github.com/ryansolid/dom-expressions

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.