8 ms·
The article did a poor job of explaining this, but I think the assumption with utility-first CSS is you’re using some component framework. So instead of having
by tlrobinson 4y ago
The article did a poor job of explaining this, but I think the assumption with utility-first CSS is you’re using some component framework. So instead of having to separate the HTML and CSS, and invent names for every child element of a component, you just use the utility classes in the component, and reuse the component rather than the (component level, not utility) classes.
- rendall 4y ago> The article did a poor job of explaining this... Yes, I agree, and that was more my point than any dig at Tailwind itself. Just because the article argues badly does not mean the argument itself is bad.