4 ms·
We just addressed this problem at work. The answer was to provide better tools that allowed users to analyze/interact with the data without having to render 10
by lukev 16y ago
We just addressed this problem at work.
The answer was to provide better tools that allowed users to analyze/interact with the data without having to render 10k rows to the screen.
It's not like they were able to read them all anyway. I'm going to go out on a limb and say unilaterally that anything that's just dumping 10,000 rows to the screen has, a priori, terrible usability.
It's not really a case I feel browser designers ought to spend a lot of time optimizing for.
- ars 16y agoThat's true, but there wasn't time (i.e. money) to design something better. It started much much much smaller, but they used it so much it grew far beyond it's initial design, and we were never able to come back to it to do something better. (It's an internal tool BTW, so we, i.e. they, just dealt with it.)
- deleted 16y ago[deleted]