| > It's basically inline CSS. It's not, because there's a system to it. With Tailwind you pick specific values. Inline styles let you specify any value. > It should not be ".text-gray-500" (like Tailwind does) This is fair. I'd never considered that specifying the actual color in the class name would be problematic, but another thread pointed out that it makes theming (such as dark mode) difficult. > 1. Select based on cascaded semantic HTML elements; 2. Don't repeat yourself; 3. No unnecessary classnames; 4. No style-descriptions in classnames. I'm sure this works great when there are a small number of people working on styles. When there are many, however, I've found that the cascade often results in styles overriding one another, and needing to introduce more specificity to fight it, in an endless cycle. Obviously people should write better CSS to avoid that. Which is actually what Tailwind is, I think. |
I think what bothers people isn't _what_ it is but _where_ it is. I for one, don't want long sausages in my HTML elements, regardless of whether they are classes or CSS styles.