Earlier quoted context omitted.
> This is what CSS classes were made for. That brings with it the problem of naming a thousand things in a consistent way that everyone on your team needs to understand and remember, otherwise you end up with tons of duplicated classes, parallel systems, and bike shedding. Have we, as an industry, not felt this pain often enough yet? Do we really need to keep banging our head against the wall to figure out it does hu…
> That brings with it the problem of naming a thousand things in a consistent way that everyone on your team needs to understand and remember, otherwise you end up with tons of duplicated classes, parallel systems, and bike shedding. Have we, as an industry, not felt this pain often enough yet? Do we really need to keep banging our head against the wall to figure out it does hurt? Of course. It's obviously better to…
Tailwind doesn't solve technical problems really, it solves social ones. In a perfect world we all write vanilla CSS. But, in my experience, it becomes extremely messy and hard to reason about in huge codebases with lots of developers. Which sucks but isn't surprising to me.