The issue is that instead of the web community as a whole working to create one awesome table widget we are fragmented across X frameworks creating X table widgets that all do the exact same thing.
I'm trying really hard not to make a snarky comment here... the fact is there is, always has been, and always will be a lot of fragmentation with any web technology.
Just like there's fragmentation with desktop apps... QT, wx, GTK and that's just a handful for Linux alone. That doesn't include all the Windows and OSX UI packages over the years... The web is far more flexible and diverse in practice, and also more open, so you simple see more of the options.
MaterialUI, MaterializeCSS and Bootstrap are all decent starting points... depending on what you want to do. If what you want is a nice table widget, nobody is stopping you from making one... become part of the web community you're complaining about...
If you aren't part of the solution, what are you? In this case you're supposed to be a programmer, with an itch to scratch... scratch, and share.
So if my itch is to create a shareable component that interops with any framework that wasn't really possible until web components came around. And of course I'm all for many different takes on the same problem. The issue I have is that there's no way for any one take to rise to the top for a given component because it usually only works with one framework out of the box. After seeing table components be created for jquery, then ember, then angular, then react, with no significant improvement on each other other than working with their particular framework, I definitely long for a universal way of authoring components so we can cut down on the churn and focus on actually building our apps.
So, you can take a QT table component and use it in a GTK app without a lot of extra overhead?
I don't see how this is really all that different from components in any language/environment/platform... yes, there is fragmentation.. and yes, you can mash things together, doesn't mean you should, but you can.
That said, it's an itch that has been scratched, if it hasn't been scratched for your tool of choice, dig into that... the fact is that more people are working towards enhancement from phone to desktop, and being able to work with similar controls at different sizes/rendering... table controls don't really fit outside the desktop model, which is probably why there aren't more options for react, and probably more for angular than react at that.
