For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
Ben Halpern -
Scott Reno -
DevOps Descent -
Jamie -
Top comments (8)
Here are a couple of posts that explain why TailwindCSS is good:
5 reasons to start using TailwindCSS
Why TailwindCSS is Dangerous
Thanks for the links.
I saw tailwind is trending now a days. Tailwind claimed it is utility based framework rather than a component based like bootstrap.
i found component based approach is a cleaner one than this utility based. discussions are welcome.
It's a matter of taste. I also prefer the modular approach, but many people including quite several colleagues of mine love the utility-based nature of Tailwind.
Everyone's personal preferences are merely subjective opinions that cannot be right or wrong, so they should never be argued about as if they were.
yes choosing a framework is a personal preference. i just started this thread on my curiosity to know from the guys who love tailwind, how this utility approach works better for them.
I'll ask my prominent Tailwind teammate if he wants to elaborate on his views :)
To me, that's because class names in Tailwind are more like CSS properties. I find it easier to remember those classes than component based classes like in Bootstrap. Btw, I've used Bootstrap & Bulma before.
Apart from that, Tailwind provides an easy way to remove unused CSS. They also have IntelliSense for VSCode.
Good to know that tailwind has the options to remove unused css and intellisense with VSCode.
i will try tailwind :)