Tailwind Is a Leaky Abstraction

Re:Tailwind Is a Leaky Abstraction by eajakobsen on Tuesday November 29, 2022 @09:44AM (#33788196)

I think the point in the comment you are replying to is that they _prefer_ having markup and styles in separate files.

[ Parent | on HN ]

Re:Tailwind Is a Leaky Abstraction by solumunus on Tuesday November 29, 2022 @10:49AM (#33789006)

You can still do that though. I swear half the Tailwind haters haven't used it for more than 30 minutes, or at all.

[ Parent | on HN ]

Re:Tailwind Is a Leaky Abstraction by xigoi on Tuesday November 29, 2022 @04:53PM (#33793887)

Then what's the advantage of Tailwind?

[ Parent | on HN ]

Re:Tailwind Is a Leaky Abstraction by solumunus on Wednesday November 30, 2022 @07:18AM (#33799677)

Standardised and clean CSS syntax. The benefits in that context are debatable, a component based frontend architecture is where it absolutely shines. If you end up using it in that context you won't need to ask this question, it quickly becomes clear that it's the optimal path.

[ Parent | on HN ]

Re:Tailwind Is a Leaky Abstraction by emmacharp on Wednesday November 30, 2022 @09:43AM (#33801371)

What can't pure CSS do here and that Tailwind does ? The CSS syntax is already clean and standardized if you use it properly and don't name every little piece of interface. It is a genuine question, by the way...

[ Parent | on HN ]

Re:Tailwind Is a Leaky Abstraction by xigoi on Wednesday November 30, 2022 @09:54AM (#33801551)

CSS is standardized…

[ Parent | on HN ]

Re:Tailwind Is a Leaky Abstraction by nailer on Tuesday November 29, 2022 @12:45PM (#33790695)

No, I have HTML and CSS in the same component file. I prefer having styling in one place (the CSS inside the component file) rather than two (the HTML of the component and tailwinds’s own postcss files that implement the styles).

[ Parent | on HN ]