> CSS modules still seem to solve every problem Tailwind solves, and better. I agree with most of what you're writing, but in arguing this out with people who

> CSS modules still seem to solve every problem Tailwind solves, and better. I agree with most of what you're writing, but in arguing this out with people who seem to be enthusiasts, what I think I've discovered is that while there are existing (hell, longstanding) unbundled technical solutions fully capable of solving the problems Tailwind does... they don't solve the practical problems of channeling a group into a good-enough design system, and in fact many people who've been doing CSS have never actually really used a design system (especially if their experience is solely recent, and definitely if their experience is only incidental in the sense that they're application devs first). And many organizations don't have roles where someone can focus on solving this problem. Just-add-Tailwind may hit an interesting pit-of-success spot for a lot of people in this position, where TW provides the atoms of the design system to scatter in a just-in-time manner. Sure, not elegantly, but practically. Personally, I'd prefer to work with people/orgs that don't see this is an optimum, but I might accept it as a situational local optimum.