> CSS doesn’t scale across teams/dependencies in its vanilla form in my experience, not at all. In your experience. It was my experience too, until it wasn't.

> CSS doesn’t scale across teams/dependencies in its vanilla form in my experience, not at all. In your experience. It was my experience too, until it wasn't. See this: https://news.ycombinator.com/item?id=39501442 https://news.ycombinator.com/item?id=39501442 > often with no way to even control/revert what some deep dependency does Without looking at specifics, it is hard to say, but it is very likely that this is a design mistake. It's very likely that the person making these mistakes is also making these mistakes in code and creating tangled messes there. The state of development is quite poor. "Average" (read: most) developers create tangled messes because it's all they know how to do and they've never taken the time to learn how not to do it. So, when something like Tailwind comes along and says "you can't make a mess with this", then of course they will jump on it. They will not, however, be very interested in recognizing the costs that come along with it. They also will be incapable of seeing that the other path is not only simpler, but it can become easier with practice.