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.
Always frustrated because your CSS styles aren't working the way you intended? You should learn more about CSS Specificity! Check out my newest blog post 🙃 dev.to/emmawedekind/css-spec…
16
51
9
314
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 ...
6
5
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.
1
8
I would love to see a mini series from you! Let me know if I can help — at minimum by promoting it.
2
3
It was getting no traction, but it was during a less active time for me. I would absolutely be grateful for any spread like butter. We need all the tools, and we need to use them well. There's a reason a hammer has a long handle. :)
1
2
I tend to like writing short form these days for pro stuff (I tire easily) but can write long form in social conversations like this or on FB. I don't see it as writer's block rather a shift in how I approach writing these days.
Jan 23, 2019 · 5:39 AM UTC
1