Still, the question remains, what's the improvement over Svelte or SolidJS which doesn't use VDOM as well ?
https://krausest.github.io/js-framework-benchmark/2023/table...
No VDom is always faster than having a VDom.
But I do agree with your point 100% that it should tell you right away about it on the README what that means, and the significance behind the claim.
IIRC in a recent stream the author of Solid showed that it's hard to beat a proper VDOM implementation when you have 1000s of elements.
And most naive non-VDOM implementations will probably lose to a good VDOM implementation.
Is there some recent study showing evidence or analysis of this? You're saying the main root cause of poor performance is the diff burning up CPUs?
I always assumed applications run slowly because people are overusing global (redux) state and every state change is subscribed to by like 10 different components. And people making 5 network calls before their component meaningfully renders.
If you're rendering thousands of items on an SVG data visualisation, sure it matters.
You can tell it matters because otherwise React wouldn't have implemented escape valves to improve performance, like shouldComponentUpdate.
You can get around this by using persistent data structures with lenses, which is how Elm works. Then it's just reference equality checks as you go down the tree, which is inherently faster.
I am not educated on the no-virtual-DOM-hype.
What actually costs more here:
(1) the diff and vdom algorithm or
(2) the actual DOM calls?
I always thought it was (2)... is this right?
That said, the big feature here seems to be what the headline says: no virtual DOM. As a user of frameworks, I don't care much about implementation details unless they result in benefits like performance improvements. Does this perform better than React and/or Vue? Or is there some other benefit to it?