5 ms·

I've worked with Tailwind in 3 separate, huge projects, and it's infinitely easier to upkeep than the monstrosity that large SCSS/CSS codebases turn into. Ther

I've worked with Tailwind in 3 separate, huge projects, and it's infinitely easier to upkeep than the monstrosity that large SCSS/CSS codebases turn into. There's no hunting down random css classes all over the codebase, no dealing with insane cascade issues, no idiotic specificity issues, no unused classes that everyone is afraid to touch because it might break some random div somewhere...

pier25 3y ago
You can still write component-based CSS/SCSS without Tailwind and that solves all problems you mentioned
- joshuaturner 3y ago
  CSS/SCSS modules are still, for me, the best option to balance maintainability and flexibility within a component
hmeh 3y ago
Have you ever tried making your SCSS/CSS codebases not a huge monstrosity? It can be done.