I’ll be honest. I’m a contributor to this. I’ve been CSS since the mid 2000s and I have a lot of it memorized by heart. My team uses tailwind, therefore I use tailwind But I don’t want to reconfigure my mental model to think in esoteric shorthand, when I already have vanilla web tech memorized. So I just write some code to match the design and then I let an llm transform it into what my team expects. I’m sharing in t…
Every project I worked on that used CSS was a mess. It's always 1000 line SCSS files and nobody knows what is going on there.
For what its worth, I had the same experience with Tailwind. I regularly see classes that don't have an meaningful outcome.
I don't think the problem is Tailwind or CSS (well, I guess Tailwind is CSS with extra steps but you get the idea) syntax (or any of the CSS preprocessors), but the fact that styling in browsers has accumulated a lot of cruft, and people who haven't "grown up" with it over the years don't fully understand it (I am more competent than most with it and there's still times I screw up).
One thing that's kinda nice about Tailwind is that it made copy-pasting components easier. So people can get something decent without fully understanding what's happening