[dmnd]

As you can see in the readme, we haven't made any accommodations for external adoption — the system is very opinionated at the moment (i.e. themes, styles, types).

But we were thinking perhaps we should spend some effort making it easier for others to use <Table /> elsewhere. How close to usable is it for your use case?

[kaivi]

It is really fine as it is for me, the custom styles don't really matter for a B2B app I am working on. Just add an InlineEdit mode to a Table, and it will be better than any OSS table component there is today!

One thing about inline-editable components and tables. As a former office drone and a part-time speditioner, I believe that such components must be tabbable, and an ideal editable table should try to mimic the desktop experience. Office workers spend thousands of hours in backoffice apps, watching 0.3s animations and aiming with a cursor, but they never complain because they don't know any better.

Just to demonstrate a different InlineEdit, here is a demo of a lib I made several years ago. It worked great with tables and card views: https://kaivi.github.io/riek/

Also didn't your former colleague write up this post on data tables in 2017? It was trending here yesterday. Looks like a lot was already implemented back then: https://uxdesign.cc/design-better-data-tables-4ecc99d23356