I Hate Tailwind and Love Bootstrap
necromant2005.github.io
I Hate Tailwind and Love Bootstrap
1–10 of 20 posts
Re: I Hate Tailwind and Love Bootstrap
#2It 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.
Re: I Hate Tailwind and Love Bootstrap
#3It just adds an extra layer of abstraction, which I happen to also find unnecessary.
Re: I Hate Tailwind and Love Bootstrap
#4Re: I Hate Tailwind and Love Bootstrap
#5Re: I Hate Tailwind and Love Bootstrap
#6Re: I Hate Tailwind and Love Bootstrap
#7I 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.
Coming back a couple of years later to a broken build system when you just want to change a colour is no fun.
Re: I Hate Tailwind and Love Bootstrap
#8If 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.
Re: I Hate Tailwind and Love Bootstrap
#9Re: I Hate Tailwind and Love Bootstrap
#10"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.