3 ms·

I think the author nailed it on the head towards the end of the article. > You still need to know CSS. Yes, that's been the position of the Tailwind team from

I think the author nailed it on the head towards the end of the article. > You still need to know CSS. Yes, that's been the position of the Tailwind team from the get-go. In the author's defense, when users compare it to Bootstrap, that doesn't help. The author isn't wrong I don't think with his observations, but to many people using Tailwind, I think the "downsides" are worth it for the massive gains in other areas. One thing I believe will be changing in v4 (tried finding relevant tweets but came up short) next year, is the a more concise syntax to eliminate much of the repetition the author identified around nested selectors. For me personally, I would probably see those types of usage as an anti-pattern or a code smell. If you need extra classes on a structured list like in the example, I would opt to add that logic to the templating loop rather than use CSS to select every 4th option inside of every 2nd other option.

aniforprez 4y ago
In my experience, Tailwind has only helped me learn and actually wrangle CSS to an effective degree. Most of the time, I'm looking up multiple articles on how to execute exceedingly simple things in CSS (the infamous vertical centering problem). Now, I only have one tab open, the Tailwind docs. All my searches give me the exact classes I need and I learn about Flexbox and all its useful properties, CSS Grids and all the other useful things CSS lets you do. I never once felt like I was robbing myself of some arcane CSS knowledge that some people gatekeep. If anything, it made CSS so much more approachable for me as someone who isn't particularly design oriented. It also made me think much more heavily about actual HTML and wrapping things in divs and spans effectively to style things in better ways