3 ms·
(I am not a real lawyer) but I think it's just little more complex to program. CPU time issues don't matter much, we can design around that. If we pull, say, 1
by tryauuum 5y ago
(I am not a real lawyer) but I think it's just little more complex to program. CPU time issues don't matter much, we can design around that.
If we pull, say, 1000 rows in the foreground, you have to keep in mind when designing UI that you have to wait for data. E.g. you have to design some sort of indication that data is not yet 100% loaded if user tries to search something in page.
Another point is that (maybe, I have no experience in UI design) that users favor fast loading page, even if it only has 10 rows..
- codingdave 5y agoIt is actually easier to just dump the whole set and put up a spinner, so I'd say no, it is not because of ease of coding. It often is needed when you have a set with a million rows. You have to show the end user what the data will look like, give them a sampling, then help them filter and sort it down to what they really want. That being said, if you show 20 rows when there are only 85 in the set, that is just a silly UX decision. Add a scrollable grid if needed, but the performance difference in returning a couple dozen vs. a hundred is fairly meaningless these days.