Hacker News Reader

Comment by boundlessdreamz | Hacker News Reader

How does it compare with https://grid.glideapps.com/ ?

Or tabulator http://tabulator.info/ .. I don't see filtering though.

I was recently evaluating a few of these to display large number of items (tabulator, aggrid, custom solution using react-virtualized etc)

Unfortunately if you are planning to use tabulator (in an enterprise environment for example), I would advice against it for a few reasons:

- No tests (atleast I did not find them when I looked into it)

- I dont normally critique the codebase but I found it to be a bit unorganized and that did not inspire confidence. Basically I found it be non DRY. However I found it easy to understand and make changes

- Being developed by one person and I found little support and response when I raised issues and PR

We've been using tabulator for few years now on an internal project. It's been doing quite well so far, has a lot of features out of the box and is easy to customize.

To balance my critique, I would add that I found that tabulator had support for most number of features out of the box of all that I tested and was the easiest to customize

Looks quite similar to me. Both are using canvas (combined with off screen rendering?) under the covers which seems to be key to achieving this level of performance.

No reason to sacrifice accessibility and styling in the name of performance: https://github.com/jpmorganchase/regular-table

Glide Data Grid has a fully accessible DOM subtree. No need to sacrifice accessibility just to use a canvas. Come on, its 2022 we have the tools. What makes Canvas even nicer is I can export a subdom that is bespoke for screen readers. It is exactly what the screen readers want, nothing more, nothing less. It works wonderfully.

Disclosure: I am the primary developer of Glide Data Grid.

Funny. I just rolled my own datagrid for a portion of a larger application that already uses DataTables for various stuff. I wanted something that acted like this, was fast and allowed for easier row and column styling (including in the data itself). Also, faster and more flexible animated resizing.

I ended up using CSS grid divs and without any virtualization on my part, they're shockingly performant. Both Chrome and FF easily handle 1m cels which is more than my use case will ever need. They're really quick at blitting just the necessary cells, making it wayyy smoother than DataTables in virtual mode. And anything on an actual canvas tag...? forget about it.

DataGridXL actually only uses canvas for cell background colors (when you use the search bar) and for measuring text width. Everything else is DOM, just not <table> with individual cells.

Reply on news.ycombinator.com