In my opinion CSS's worst sin is that it does not include basic experience from other programming languages: variables and name scoping. It's a minefield of namespace collisions and superfluous repetitions.
Or they say from the highest and mightiest and ivoryest pedestal "separation of semantics and display, thus spaketh the lord" pretending, of course, that modern websites look and behave just like documents when that's demonstrably false, and that tables are therefore irretrievably bad.
And instead you now have, 20 years later (TWENTY! YEARS!) something that only now works as well for layout.
Adding "not-data" and navigation directives to tables to aid screen readers and separate semantics would not have taken 20 years.
And now you'll have to wait another 5 years before this new, "just as good as tables!" feature is sufficiently widespread to actually deploy it without a polyfill shim.
But please tell me more about what I do or don't know.
To compare things: Knuth's TeX has very few basic primitives: boxes, lists, and glue. And it produces very sophisticated layouts. CSS has a wagon of stuff and still cannot produce very basic things. I sometimes remember the old Ventura Publisher software (in 1990 I worked with version 3 of it). It was somewhat similar to the current HTML+CSS: you could have the same source text, but separate style files that would render it very differently for different purposes. 27 years ago.