[mattstir]

I'm curious about this. I'm not a frontend engineer but enjoy tinkering on simple frontend UIs for my hobby projects, and I've found Tailwind nice for creating encapsulated components more easily. It's funny that it skips the entire cascading part of Cascading Style Sheets though. Are there major downsides besides that?

[seanwilson]

> It's funny that it skips the entire cascading part of Cascading Style Sheets though. Are there major downsides besides that?

I think cascading is a bad default. It's useful, but only sometimes, and often causes headaches like unintended coupling and confusion about why rules are being overridden. The utility class approach (like Tailwind) makes a lot of issues like this go away. I don't see a good reason why the traditional approach is worth the extra pain or discipline.

[atoav]

CSS can be laser-like specific if you want it to. Want to only affect that thing? Use ids, inline styles or learn how to write proper selectors.

I am by no means a CSS expert, but 90% of CSS issues I heard complaints about boiled down to the complainers not having spent the time necessary to learn the basics. And the other 10% were solved by :has()

That being said, most other styling solutions I had used (e.g. in GUI libraries) will quickly make you wish you had CSS.

[Klonoar]

Yes.

The cascade model is a bad design.