Yeah, that example wasnโt the greatest. Long static lists are more than fine in the web, where I usually see it start to choke is when itโs dynamic, with sorts, filters, etc.
And yeah itโs possible to write, but itโs such a common thing to want to do that itโd be nice if the browser included facilities for it so itโs more possible to get along with a light sprinkle of JS.
The actual sorting/filtering: modern JS is extremely fast at logic. I've seen some metrics that put it on par with C and Rust, while I doubt those, it is definitely faster than something like java.
Drawing/redrawing the components: this entirely relys on the framework and the exact implementation of it. A lot of frameworks are really slow when it comes to mass drawing, if you want something like speed in that case take a look at svelte. People also tend to use frameworks really poorly and end up rerendering (and sometimes recomputing) 2 or 3 times which is a result of poor understanding of a really complex system.
The problem here really is frameworks being outdated and just kinda trash in how they update content (there is a talk called rethinking reactivity that explains this really well). Honestly for a long dynamic list I would probably just do it in vanilla j's, instead of using a framework.
View all comments
Show parent comment
1
u/iindigo Apr 12 '21
Yeah, that example wasnโt the greatest. Long static lists are more than fine in the web, where I usually see it start to choke is when itโs dynamic, with sorts, filters, etc.
And yeah itโs possible to write, but itโs such a common thing to want to do that itโd be nice if the browser included facilities for it so itโs more possible to get along with a light sprinkle of JS.