[al_borland]

When I see people use Tailwind they are adding a dozen classes to something to do what a single class in Bootstrap does.

On a component that only needs to be defined once, no big deal. But if you need to add this collection of classes on 20 elements, adding a bunch of Tailwind sounds messy and error prone.

Tweaking Bootstrap here and there sounds a lot better than using 100% tweaks. Tailwind seems like a tweak library. Add 10 tweaks to each element and you start to have a design on your hands. I often question why it exists vs raw CSS.

[TheCapeGreek]

Which leads us to: Tailwind supports making your own components, and encourages it. But devs, either pressed for time or lazy, or by always getting a slightly too unique design from their design team, don't do it.

At the same time, not everything is a reusable component, so yeah, shove a couple dozen tailwind classes there and call it a day. Still better and less messy than hand-wringing custom selectors or custom element styling - else Bootstrap would be better for tweaking than "100% tweaks".

It's the usual OOP debate on inheritance vs composition.

Tailwind is composition, and it's clearly the favoured approach.