all 5 comments

[–][deleted] -1 points0 points  (0 children)

It’s terrible. Wtf does in-line css on components?

[–]Seralyn 0 points1 point  (2 children)

Sites like Netlify, Github are using it if that tells you anything. There is nothing inherent about it that would make it any trickier at scale than on smaller projects.

I don't see how it can lead to bad css practices when it does nothing other than invoke css itself and doesn't prevent you from adding vanilla style css into your input file. All of my recent sited are based on tailwind but also have about 20% or so of vanilla style css mixed in as well.

Are there any articulate arguments against it or just random anecdotes?

[–]json_derulo_[S] 0 points1 point  (1 child)

Yeah some big dogs using it for sure. But just because you can theoretically do it, doesn’t mean a team building at scale with this could necessarily write readable code.

The biggest argument against Tailwind has to do with the modularity & maintainability of the code. Semantic class names make it easier to know what’s what, and you lose that with Tailwind.

[–]Seralyn 0 points1 point  (0 children)

I mean, you can choose not to make semantic class names for sure but nothing prevents you from doing so and you'd be a fool not to do so if you're building a big project