React smoothly redrawing ~20,000 dom nodes. but yeah I'm sure it's too slow for your crud ui

Mate, this is too many dom nodes for chrome devtools to work (takes 10s to open inspector). Of course it noms memory

This is why I’m skeptical of rendering libraries that run micro benchmarks showing how they are like, soooo much faster than React. React is already fast enough.

I mean the problem with React is it is too easy to shoot yourself in the foot and cause rerenders. It is one of the reasons I am more bullish on signal based systems like Solidjs

But imagine how much quicker it would be if you wrote it in Rust and complied to WebAssembly and… never shipped it?

There are no memos in here btw But I do use React Query to load data with stable object identities

In tradeoff of huge memory.

Oddly I've seen it to be slow on large forms that rerender on every keystroke (at least this was react 16). 2-4ms for render function to complete, 100ms for react to diff and patch. The fix that made a difference was to memoize the vdom and bust cache on fields that need change.

DOM nodes never were the issue. The JS re-render part is. Try putting 1.000 controlled material ui checkboxes without memo or anything and see it crumble

Not talking about premature optimization here, but this should be canvas. Why 20,000 nodes for a display that could only reasonably display (4k) about 1000 of them horizontally, this is a usability problem too. What happens if you compare 10 of them below each other?

probably worth noting this here too