Edit: The core concepts section is worth a read in it's entirety but I believe this is the relative part:
https://tailwindcss.com/docs/reusing-styles#avoiding-prematu...
But, this component needs a little more padding here and not there. We need flexbox - which parts? Some. Some here, some there, but not all of it…yet. What about grids? Sure, maybe, how? Media queries spread all over the place wrapping things arbitrarily. Oh! And scoped styles every which way for that component-specific flair!
Our component class declarations are about to get a lot more verbose, and I’m all for it. I’d much rather see that, and know what the visual structure should be, instead of tracing a class back through mountains of tacked-on SCSS to add a child class that gets applied in one place that makes a thing have zero margin.
I'm curious if this was all done on github, or if you and the PR submitter discussed the cleanup via other channels before they just blazed ahead with the refactor
Those unable to walk will always trade in their crutches for wheelchairs.
That's not true at all. I have been one of the earliest adopters of Tailwind and it is 100% enough for me and has been for 5 years.
I could rant, but I'll just link Casey Muratori's take on CSS instead. https://feeds.resonaterecordings.com/software-unscripted
