[jackdh]

My point is that there is no one CSS library to rule them all and likely never will be. The closest to that is going back to pure raw CSS which I highly doubt people will do.

And yes while it's obviously not ideal to have a hundred competing libraries in your code, you can create what works for you / your team.

[pier25]

> The closest to that is going back to pure raw CSS which I highly doubt people will do.

Huh? Tons of people write vanilla CSS which is getting better every year.

[const_cast]

Very very few people, in practice, write vanilla CSS. They use libraries and frameworks often, like Bootstrap. Sure, that might be "vanilla CSS", but you didn't write it, presumably because you didn't want to.

Look, after a certain point we have to call a spade a spade and acknowledge that CSS is just too cumbersome, too awkward, and too complicated for most developers and companies. How much CSS do you see that seems to be read-only? People just... tack on to the end of the style sheet, right?

The promise of re-usability is great, but is it actually happening? IME, no.

[pier25]

> Very very few people, in practice, write vanilla CSS.

That's not what I've seen. Most frontend developers I know usually write CSS (or SCSS previously).

> CSS is just too cumbersome, too awkward, and too complicated for most developers and companies.

Really?

I disagree but are you arguing TW solves any of that?