3 ms·
> Not having to come up with names for CSS classes As soon as you want theming you'll need to start naming stuff. And if you want that theming to support third
by Rapzid 3y ago
> Not having to come up with names for CSS classes
As soon as you want theming you'll need to start naming stuff. And if you want that theming to support third-party CSS overrides, or need good CSS selector support, you're going to be back to needing to name classes again.
Not everyone needs that, and that's fine. But there are plenty of people working on products and in environments where the Tailwind way is not going to be the path of least friction.
I would actually say StoryBook, or the StoryBook pattern at least, has been a much greater boon on FE development over the last decade.
- braden-lk 3y agoA nice thing about tw is you can set your colors, paddings, etc, to resolve to CSS variables. That + some tweaks to the tailwind config, you get a nice themeable setup that doesn’t deviate too far from vanilla tailwind, imo.
- gedy 3y agoSomewhat - but when your theme change does things like "buttons are now green outlined rectangles instead of blue filled rounded corners", Tailwind shows its weaknesses. DaisyUI on top of Tailwind helps, but then you may as well use Bootstrap and get better component support.