Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Good point about the UX. I haven't really found a good way to navigate 2000 questions, but they are divided in sections so that could be a first step. I guess the idea is to not render the questions I cannot see anyway. Then again - something like this jsfiddle.net/hkwdw77c using jQuery seems to have decent performance . Commented May 17, 2016 at 10:58
  • While you should be able to get a few thousand rendering quickly, it really shouldn't be done that way. Users are only ever going to see x at a time, so things like infinite scroll can make the page appear as though it is rendering as many as you want without the processing overhead. Commented May 17, 2016 at 11:02
  • 1
    Also I found clusterize.js which seems to fit my use case. Example with search. Commented May 17, 2016 at 11:03
  • 1
    Thanks. And for React this might be a good place to look: github.com/bvaughn/react-virtualized Commented May 17, 2016 at 11:24