re: Is the Tailwind approach a big step forward for CSS or just-yet-another-thing? VIEW POST


My personal theory is that Tailwind is a joke that nobody really caught.

A few arguments:

  1. If you're writing your CSS in class instead of <style> well so be it but you're still writing it.
  2. How exactly do you justify to yourself putting so many classes and copy/pasting so much code? That's not DRY, that's the middle of the ocean where Tailwind pushes you to.
  3. You need complicated tooling to use it right. Do we really need more tooling for something that is basically Emmet in class?
  4. But mostly, writing good CSS is about intent. I don't see anybody documenting their CSS but I put comments on every single CSS selector in my code to explain why they are here and why I made those choices. Same thing goes for variables, even if I never change the value, by reading an expression I can understand how I got this margin size. And you get absolutely no chance of doing that with Tailwind.

I'll sum this up that way: if you can't document it, why even bother using it?


Tailwind is more than a joke. It's a terrible joke.

code of conduct - report abuse