Tailwind CSS Debate
The cluster centers on debates about Tailwind CSS, including its benefits for accessibility and productivity versus criticisms of readability, performance overhead, and deviation from traditional CSS principles.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Doesn't this miss the point with Tailwind and why we have Tailwind in the first place?
What's wrong with tailwind? It made css styling accesible and easy at least for me.
With tailwind people aren't writing CSS anyway (technically)
CSS is great now, tailwind is an unnecessary overhead.
AI for CSS sure, but why tailwind? Why limit yourself like this
Tailwind might not be the most perfect fit, but it's "just" CSS.
Can you elaborate on what problem tailwind is solving? My first impression is that it looks like a set of custom built css classes.
I had the chance to use Tailwind recently. I don’t think it’s disputable that in a sense it mocks the “cascading” part of CSS, though I’m not sure I’d hold that against Tailwind. It often felt as taking a shortcut to me, but it could be a worthy tradeoff and so far I have not noticed Tailwind overly complicating maintenance and development of an average project. That said, I don’t think I would choose Tailwind if I could use, e.g., web components with scoped styles or something similarly more i
Doesn't that negate most of the benefits of using Tailwind in the first place?
Solution: don't use Tailwind.