I’m convinced 40%+ of the anti-CSS complaining is out of frustration from folks who haven’t actually learned how Specificity works. I wrote CSS for five years before I knew this is a thing I needed to learn. It was @mholzschlag who taught me, at a presentation she gave in NYC.

I've been thinking a lot about this issue today and don't think it's an issue of anti-css but what is fast and easy. An example is encouraging inline CSS, or cheating with a !important without knowing where a conflict is, causing potentially more conflicts down the road ...

Too much focus in the last years on performance over quality browser development and the nuances that exist between them. I made an entire career on the subject! And it feels crappy because we didn't keep at it after 2015 and the rise of frameworks. I'm going to do a mini-series.

I would love to see a mini series from you! Let me know if I can help — at minimum by promoting it.

I start with Cascade, Inheritance and Specificity. It is for folks who know selectors and some CSS, but I keep it as simple as possible code-wise as I'm focusing on the technology of the browser which is where the real technical aspects of specificity and browser engine meet.

I bet I saw some version of this talk in NYC. Total game changer.