3 ms·

I can't speak for others but I'd imagine you are talking about two different things. There's "learning css" in the sense of learning all the syntax & semantics

I can't speak for others but I'd imagine you are talking about two different things. There's "learning css" in the sense of learning all the syntax & semantics. Tailwind does not help you here at all. Then there is "learning css" in the sense of using it decently. Meaning proper spacing of elements, good typography, etc.. A design system if you will. This is where tailwind steps in by providing very reasonable defaults for a lot of things. The advantage of tailwind over a full design system is that it is piecemeal, you only pay for what you use. It really makes a lot of sense when combined with a component system like React because you get re-usability at the component level instead of the style level. I like this a lot, but it may not resonate with everyone.

warent 4y ago
I think they're referring to my comment and yes your interpretation is what I intended to communicate. Give me a picture of a dream website and I can easily write all the CSS and HTML to create it identically and responsively as I have done for years. But give some general product description, and no amount of CSS knowledge will save the monstrosity I create
ehutch79 4y ago
Oh, the design system aspect of tailwind is GREAT. The idea of utility classes is super helpful. I was actually pretty into tailwind at first for these reasons. There were some issues, most of which were fixed with the JIT. That said, most of the hate for tailwind is due to the 'community'. People saying to just take the best parts are the minority of opinions you see on tailwind.