4 ms·
My app has some huge tree (CRUD-able). Say 20k-30k nodes (sweet spots for being usable without virtualizaion). And Chrome perf sucks real bad for "Recalculate S
by Existenceblinks 4y ago
My app has some huge tree (CRUD-able). Say 20k-30k nodes (sweet spots for being usable without virtualizaion). And Chrome perf sucks real bad for "Recalculate Style" phrase" the `.tree ul li::before{content:''}` is going to be ruining perf. Meanwhile firefox is wicked fast for overall perf for lots of dom nodes.
- equalsione 4y agoWould you consider using d3.js? I’ve been able to get great performance for large deeply nested trees using d3. It depends on your use case of course.
- Existenceblinks 4y agoIt's 278.58kB(.min), I'm not sure how good its tree shaking is. I pick every js dependency seriously. Generally libs < 7kB gzip for each.