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.
tmnvix•31m ago
I agree. But also, on a broader note, I have no desire to introduce node for the sole purpose of some css niceties.
Coming back a couple of years later to a broken build system when you just want to change a colour is no fun.
ricardobeat•1h ago
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.
ceritium•54m ago
Me too
jaapz•34m ago
Ah, time for the pendulum to start swinging back again
jdmoreira•32m ago
Just use DaisyUI
rahimnathwani•23m ago
"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.
rmykhajliw•2h ago
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.
tmnvix•31m ago
Coming back a couple of years later to a broken build system when you just want to change a colour is no fun.