Fabio Spampinato

IMO a workable solution for this is the following: 1. Custom components expose a custom prop for receiving regular refs. 2. Custom components attach those refs to a native element...

Is that like some special partition/drive? I've never seen that 🤔

Triggering hundreds of writes to the same file in quick succession is kind of a separate problem at the app level, you probably shouldn't do that to being with.

That's super interesting, thanks! Locally I've been benchmarking Voby against Solid, and there I see Voby using ~2MB less memory than Solid with 10k rows, so the result seems consistent...

> When I create 10,000 rows by manual testing and look at the memory tab I see the following: That's pretty interesting, I don't actually know what that number actually...

FWIW a bunch of people seemed to find this new test interesting: https://twitter.com/fabiospampinato/status/1542083521598169088

Obviously this is a benchmark, the actual ratio of DOM nodes to reactive bits may be different in a real application, the number of those things may be different, other...

> It does, one of the main reasons why React was "invented" is to avoid incremental algorithms when working with an application state, so they can just diff UI tree...

> Let's take for example one-to-many scenario, it can be something like results table in this benchmark where we need to calculate background color for each cell. When minmax value...

> I mean that if your application is built from small reusable components (Fluent UI, MUI, etc), you'll have ~1 DOM Node per reusable function/component and template cloning optimization will...