After the initial hit, the browser will cache both, and the load is instantaneous until it is updated again. Ok. That's pretty much the definition of normal H

After the initial hit, the browser will cache both, and the load is instantaneous until it is updated again. Ok. That's pretty much the definition of normal HTTP caching policy though. Many other frameworks don't handle things very well when the number of rows grow beyond 1000 or so, and memory consumption gets out of hand very quickly. Fair enough. Obviously you've got the UI down as it's butter smooth once everything is loaded. But many of the popular JavaScript grid systems already have stuff like virtual grids, and have had them for a while (scroller[0][1] for datatables was released in 2012 for example). They may not be quite as smooth as yours, but the DataTables example[0] (timing from the moment each has started loading of the data until there is some visual data on the screen) is less than 300ms, whereas yours is still over 10 seconds (not a 100% comparison as yours is 5MB of data). Definitely rather have people working on actual product, rather than waiting 30 seconds to do something (and each time the dropdown is switch to another country and back it's another 5MB download and 30 second wait). we offer progress options for this Then please, please show this. Showing people a demo of good code doing smart things is a great first impression. For example, a demo of 5 million rows of data via server side processing with that butter smooth animation would be amazing. Then when people are hooked, and start asking about doing stuff like loading 100% of their giant files into browser memory, you can impress them more with how there is no slowdown other than the pain they cause themselves by not loading data piecemail. But ultimately, any demo that takes 40 seconds to load is just going to be unsavory without a lot of context. [0] - http://datatables.net/extensions/scroller/examples/initialisation/large_js_source.html http://datatables.net/extensions/scroller/examples/initialis... - client side scrolling through 50k records (generated inline rather than downloaded, making for an unfair comparison) [1] - http://datatables.net/extensions/scroller/examples/initialisation/server-side_processing.html http://datatables.net/extensions/scroller/examples/initialis... - infinite scroll on server side processing of 5M records