Hacker News Reader

Comment by Gladdyu | Hacker News Reader

What would be your use case? Apart from this being a nice feat of technology and the possibility of loading the data asynchronously, in what scenario would it be practical to present 1K+ rows of data to a user? It's infeasible or at least very impractical to examine them by hand - some sorting/filtering possibility is necessary for large datasets and if your filters still return 1K+ rows you could have filtered on something more specific.

View on HN

Online spreadsheets. The end users are conditioned already on how to navigate with find, home, end, etc.

Edit: Seems like it might break on-page find though, right?

Most users don't use on-page find though. Facebook use this "lazy-load, eager-unload" for their news feed. It's a bit annoying, but obviously the alternative is your browser screeching to a halt.

If you are working with unfamiliar data it is very useful to be able to view a huge number of rows in one go. It is the kind of tool that coders all have and use but is unavailable to the general public. Of course excel should be able to quickly scroll through millions of rows if that is what the user wants. Filtering maybe the next step but you need to feel out the data first to know what to filter.

Also, it makes a certain sense to over-engineer this kind of technology to give other elements of the stack some leeway. Lazy loading is great but so is pre-emptively loading data in case latency rises.

Maybe in the case of logging or where the web page is constantly showing new data.

An example I can think is a web based interface for controlling a drone. This could be used on the page to store the timestamped output of various sensors.

It would allow for the data to be displayed while also maintaining a history of the data in the browser. Could add in filters and searches as well as a pause functionality to review the historical data.

Sort of like a dmesg for the web page. I'm thinking practical uses are sensor monitoring and server monitoring.

I think it is more trying to show that it can handle & display extremely large datasets without crashing or lagging the browser.

I recently had a scenario where I needed to have a table that could be scrolled, and needed to be able to display up to 15k rows.

At the time I went with SlickGrid[1], but this seems like a nice alternative.

[1] https://github.com/mleibman/SlickGrid

I am using SlickGrid on a current project and have had great results.

There was just a post on django.reddit.com asking how to display over 18k rows. Of course the developer knew this was not practical but business demanded it.

https://www.reddit.com/r/django/comments/3hlhgq/best_way_to_... asking for a

Financial trading applications often need big grids of data - take a look at openfin...

Reply on news.ycombinator.com