I Hate Tailwind and Love Bootstrap

rmykhajliw

I don’t believe the Tailwind approach is a stable, scalable, or reliable solution for large, long-living products. It works well for fast delivery, prototypes, and teams optimizing for short-term speed, but over time it tends to spread styling decisions across markup, making the system harder to control, reason about, and maintain.

ricardobeat

What happens in practice is you use Tailwind with components (React or otherwise), so you build `<Button primary>` using tailwind classes internally; this is functionally the same as the boostrap classes, but can standardize much more than styles. It just adds an extra layer of abstraction, which I happen to also find unnecessary.

jaapz

Ah, time for the pendulum to start swinging back again

jdmoreira

Just use DaisyUI

rahimnathwani

"Bootstrap takes the opposite approach by limiting flexibility and embedding decisions into predefined components." If you choose tailwind, nothing is stopping you from using components. You can choose to use predefined components, or you can create your own. Or some mix.

MK_Dev

Tell 'em! I also hate React and love Razor, but most don't seem to share that sentiment

bentocorp

I am missing the point of Tailwind? Don't you get the same effect and functionality from simply adding style attributes directly on the elements in HTML? Why is that approach considered bad practice, while Tailwind, which is effectively the same – but with shortened names – accepted as common practice? As the article states, at least with Bootstrap you are sharing common behaviour with a single class name that can then be modified globally.

mardix

DaisyUI[0] is the Bootstrap on Tailwind. Bootstrap makes everything looks the same. With Tailwind, most of the times and besides the colors, you have to look in the code to know it's Tailwind. [0] https://daisyui.com/