he/him 
According to GitHub, react-virtualized runs out of memory after 1B rows. 
Don't tell anyone though.
Show this thread
-
All joking aside, I think UX is questionable after 10k or 100k rows. Even if perf is good, what needles can you find in that haystack?
Show this thread
Yeah, when you have that much data to visualise seems like there’s far better ways to do it. How do you even find anything with that much?
-
-
No idea. B'c of max element size limits, RV would end up compressing things a ton so small scrolls would jump through huge numbers of rows.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.