Live data from Hacker News

Show HN: 1 Million Rows

1mrows.pages.dev

21–30 of 44 posts

Re: Show HN: 1 Million Rows

#21

Not 100% sure what I'm looking at here? Am I missing something or is it just table of data with an "infinite scroll" that loads 200 records at a time?

Loading more than a few thousand rows on a web page will make unusably slow. Especially when you add a lot more features to it. This is such that only what's seen or about to be seen is put on the page. The rest is kept ready on the server on local memory depending on what the user is doing. This allows for a scalable solution that allows you to view thousands of records and interact with them

> This is such that only what's seen or about to be seen is put on the page

This reads like it's a lazy loading library, but then the roadmap has features like

> Assign Items to Users

> Kanban View

> Collaborative Editing

Which read like something you'd have in a project management solution. How do these two concepts form a cohesive product and who is the target audience? I've seen my fair share of Jira and Trello hellscapes, but I doubt Kanban boards with more entries than memory can handle are very common.

Re: Show HN: 1 Million Rows

#23
Having the column widths jump around while scrolling and the absent page search doesn’t seem like ‘rock-solid reliability’ to me.

It seems this is just a minimum implementation of a ‘virtual list’.

Re: Show HN: 1 Million Rows

#24
This is terrible and not worthy of HN front.

Terrible from the front-end side of implementation: - performs worse than your average arbitrary-amount-of-rows-that-won't-fit-on-the-screen library (it should perform the same no matter if its 1k, 1m or 1mm rows) - is seemingly buggy - is pointless on its own, because THIS demo is a client-side demo, and no one loads that much data on the client-side.

Revisit this when this demo is performant AND data is loaded from the backend.

Ignoring that, every front-end JS developer should explore these kinds of libs and also try to implement them themselves, because they're basically front-end 101.

Re: Show HN: 1 Million Rows

#25
I'd trim the columns down to a few and show the user a filter with the displaying columns turned on and let them know that they can toggle more on.

The column text length too should be trimmed to a uniform max-length except when clicked on. You could make it pup out on the page with CSS.

A better color scheme too won't hurt.

Had the same idea when I saw https://github.com/rowyio/rowy.

Stumbled on an idea while reading a HN entry a few days back and now I will merge them into a niche product idea.

└── Dey well

Re: Show HN: 1 Million Rows

#26

Not 100% sure what I'm looking at here? Am I missing something or is it just table of data with an "infinite scroll" that loads 200 records at a time?

Loading more than a few thousand rows on a web page will make unusably slow. Especially when you add a lot more features to it. This is such that only what's seen or about to be seen is put on the page. The rest is kept ready on the server on local memory depending on what the user is doing. This allows for a scalable solution that allows you to view thousands of records and interact with them

I'm not so sure that loading "more than a few thousand rows" is as bad as it used to be.

I did some quick benchmarks a couple years back. It's been a while but I want to say that Chrome was drawing 10k rows of a decent size each (10 columns of real world data and about 500b/row iirc) in about 300ms on a 10 year old MBP.

I'll do a little benchmarking later today if I get a chance.

Re: Show HN: 1 Million Rows

#27

Not 100% sure what I'm looking at here? Am I missing something or is it just table of data with an "infinite scroll" that loads 200 records at a time?

Loading more than a few thousand rows on a web page will make unusably slow. Especially when you add a lot more features to it. This is such that only what's seen or about to be seen is put on the page. The rest is kept ready on the server on local memory depending on what the user is doing. This allows for a scalable solution that allows you to view thousands of records and interact with them

Here are some things that are already built that do what you are building:

https://github.com/bvaughn/react-virtualized https://github.com/bvaughn/react-window https://tanstack.com/virtual/latest

Post reply on HN