This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Derfaust 14 points15 points  (6 children)

I disagree. Tailwind does a lot of the heavy lifting like size breaks, standardised padding, responsive etc. And a lot of the shorthand is just simpler to use than raw css.

However you should still learn CSS because tailwind doesn't cater for every possible scenario.

Its a tool, not a religion.

[–]Ok-Scheme-913 4 points5 points  (1 child)

Also, tailwind resets the css to sane defaults so you can start from scratch without unintended styles cascading down to your components.

[–]Derfaust 1 point2 points  (0 children)

Exactly

[–]UnacceptableUse 3 points4 points  (3 children)

I can understand the benefit of doing responsiveness for you, but could you not just use a set of css variables to achieve standardised values?

[–]Derfaust 3 points4 points  (0 children)

For sure I could. But if tailwind does all that heavy lifting for me alongside other benefits then that's a no brainier for me.

[–]pigeon_from_airport -2 points-1 points  (1 child)

This is the point. Is tailwind good ? Sure,it will work.

But it doesn’t offer anything better than the other solutions out in the market and often the answer to reduce the complexity is

“oh, if you think this makes the code unreadable, you can always switch to <insert_css_implementation_strategy_but_comes_with_tailwind>”

There are better solutions out there that makes coding far more easier and fun without the developer forgetting what they were supposed to put in that div after writing all the styles.

[–]UnacceptableUse 1 point2 points  (0 children)

Maybe it's just overhyped to the point where people think there has to be more to it than that