A simple table of cards doesn't really need a custom component, but every feature you add on top of it adds up. The Kanban widget source is about 250 KB. Even if you only need ~20% of the functionality, that's still around 50 KB - quite a lot for a demo.
> Also, what's the buy in ecosystem, cost for the app payload? Especially if you're already settled on say MUI, Mantine or similar.
It's designed as an addition to your current framework/design kit, not a replacement. Most things can be configured without diving into the source, though it does take some time. So the choice is invest N hours re-creating the same UX yourself, or N/4 hours on gluing and adjusting.
Most probably, Canvas will not provide a lot of improvement. Existing JS solutions (SVAR, DHTMLX, and Bryntum) already monitor which parts of the final chart are visible and render only those. The algorithm that selects data to render is the real bottleneck on big datasets, not the rendering itself.
As for WASM, the scheduling part may benefit a lot from moving to WASM. From similar projects in the past, it may give a 2x-3x boost in calculation speed, minus the time spent on sync between JS and WASM models. On large datasets, the time for data sending (serialization and deserialization) can consume a significant chunk of the gained boost.
mkozhukh 20 days ago. link 1 point ▲ ▼