That's because everyone has a different set of requirements.
Throughout my web-dev career, I did table or detailed-list views many times, but each time with different requirements. Aside from sheer size of code to implement all the features, you will have contradicting requirements and there is no one-size-fits-all solution.
Top concerns are:
1. is your data homogeneous (all columns in a row are presented equally)
2. can this data change?
3. is there a lot of data? (so you have to implement virtual list)
4. is data dynamically loaded?
5. do you need actions on data, and how to display them (inline / overlay / menu?)
6. some features are really simple on surface (resizing, drag-drop reorder of rows, auto-sizing on dbl-click is a hell of itself) but are pain in the ass to implement.
7. is filtering/sorting done on a client or you have a server to help you?
8. and many many more...
There are multiple implementations, but you have to investigate which one fits you need.