a better approach?

[NullVoxPopuli]

Somehow this one uses wasm

https://github.com/warper-org/warper

[arthur5005]

Was looking at this, looks pretty straight forward to port, I might have a crack at this in the next couple weeks.

[arthur5005]

Got it working pretty quickly, had to copy the wasm binary in, but the wiring of it all up in a v2 addon blueprint was pretty straightforward. Got Claude to port over the test app into ember as well so I could try and make an apples <> apples comparison

Something's to note:

1. Fixed height works great, and renders more often than the react one (due to the nature of ember's reactive model) without any degradation. Can get even better frame-rate if you double raf at the expense of the render list being a tad behind (still better than react)
2. Supports scrolls way larger than a scrolling div can normally support through a scroll multiplier calculated from the rust binary /w fenwick tree. Which is awesome.
3. Their variable height demos are only supported through a calculation function you pass in, and is called at render time to feed into the fenwick tree. So huge lists take a long time on first render. https://github.com/warper-org/warper/blob/main/react/hooks/useVirtualizer.ts#L322-L325

On the third point, in order to get feature parity with VerticalCollection, we'd have to implement a dynamic calc phase during render. Radar some some dark magic, I still haven't fully groked, including how it re-uses components (which once you know what it's doing... is really easy to break)

The rust data structure does have the API to support updating itself dynamically such that we could feed new measurements lazily, but that orchestration happens in a component framework's own render phase (which, fair, we're not expecting the binary to magically be able to make dom measurements in a separate thread)

Do we:
a) just make a straight port of this, with the caveats listed
b) create a version of vertical collection with the rust / fenwick tree backing it, along with dynamic measurement calculation support

[NullVoxPopuli]

that's exciting!

do you have a repo or anything to share?

do you know what the file-size impact is?

[NullVoxPopuli]

@arthur5005 we just released v5 of this library -- which makes it a normal npm library -- which would be a good starting point for trying to integrate warper, I think?

[arthur5005]

Yeah sounds good.

Haven't look at the file size yet, but I'll get up what I have today as it's own repo for reference (apologies been busy with work that $s).

The radar /w component re-use has actual issues imo, but changing the underlying data structure for where we write and read stored measurements to be backed by warper, probably isn't a huge lift.

Only thing I wish they'd do is break the warper wasm into it's own package. I'll try and get an issue opened today with them to see if it's something they could do, because right now there's a package dependency with React.

[arthur5005]

@NullVoxPopuli
https://github.com/arthur5005/warper-ember