3 ms·
Then you're using the equivalent of bootstrap or bulma. You're not really doing anything benefiting from utility classes. And if you're going to use tailwind u
by ehutch79 4y ago
Then you're using the equivalent of bootstrap or bulma. You're not really doing anything benefiting from utility classes.
And if you're going to use tailwind utility classes, they're mostly one for one with a single css property, so you're learning something that is functionally similar to, but not css.
- warent 4y agoLogically it may be "equivalent" but I use Tailwind also because of an emotional aspect--Bootstrap et al. feel extremely dated. When Tailwind feels dated I'll be here to champion the new hotness too.
- jmull 4y agoIf you pull prebuilt tailwind components and that's it, then, yes, you aren't doing anything different than bootstrap, except for a somewhat different default look. The advantage to the tailwind approach is that all the utility classes are right there, ready to be adjusted. It's designed to expose all the "buttons, dials, and levers" needed to customize in whatever direction you want to go. (Not that bootstrap don't have customization options too, but the barriers are higher and the directions you can move in are less flexible.)