2 ms·
A good search ui should allow you to specify number of hits, imo. But 1000 would present technical problems. I'm most experienced with React and it would be dif
by schwartzworld 5y ago
A good search ui should allow you to specify number of hits, imo. But 1000 would present technical problems. I'm most experienced with React and it would be difficult to render that many rows of anything in a useful way.
Additionally, depending on how your backend is designed and your choice of ORM, sometimes requests can be slow. In those cases it probably makes sense to design a UI that encourages users to rely on search and filter controls vs giving them a large list.
- quiffledwerg 5y ago>> React and it would be difficult to render that many rows of anything in a useful way That’s not true it’s dead simple to display 1,000 rows can you explain what the hard bit is?
- schwartzworld 5y agoIt's easy with static content, but React tends to run into performance issues with long lists like that. Generally the way of fixing it is virtualize the list. Basically check the window scroll position and only render rows that you need to, instead of the offscreen rows. Twitter does this well, but I'm not sure you'd be able to Ctrl+F for text that isn't rendered.