Tailwind css is great bc i have no idea how normal css works

The Tailwind website clearly proves that the Tailwind devs don't know how CSS works, either.

@Fast-Nop just checked it out, you know you're in for a wild ride with a website that starts '“Best practices” don’t actually work.'

@MM83 Have a look at the HTML source code, and you're in for some WTF in particular on a CSS related website.

You can correct me if I am wrong but I have never appreciated Tailwind
It's a stupid idea for me, sounds like inline- css with extra steps. It "scales" because you reduced every property to class names atoms and imo it fucking suxks.

@Fast-Nop yeah right, that's some fun, readable code right there.

His blog is quite interesting, he does make some good points but it seems to me like he's taken "CSS best practices are really hard to adhere to" to mean that they are fundamentally wrong. There's some merit in pointing out that a pattern which constantly encourages you to take shortcuts could be flawed - but it's hardly the first pattern to do it, and the solution is not to just use a worse pattern.

The contention that separation of concerns is a false notion because your 'CSS will always end up echoing your HTML structure' seems to me to mistake what SOC means in this context: splitting files into HTML/CSS, not entirely decoupling CSS from HTML, because it literally exists to style the HTML - as such, it would be insane if it didn't echo it.

I don't doubt that it's faster and easier to get a page looking good, but you could use mixins to merge all those classes afterward. Keeping it inline is nigh on unreadable.

Oh hell no! I was aware of Tailwind before but now’s the first time (prompted by this thread) I took a look. Who tf thought THAT was a better idea than plain ol’ CSS? Gosh… hell to the nope. Just use Sass, o-kurrrr?

Think of CSS like this: CSS is just endofunctors mapped upon discrete epsilon-Hilbert space of metamonads. It becomes instantly obvious then

I really like it - made me so much more productive. But it's essential to split up your HTML into small components. Otherwise it's a nightmare to maintain.

@MM83 @Fast-Nope new drinking game: inspect the source code inside of the landing page for Tailwind CSS and take a shot for every span tag you find

@AleCx04 I did my math and lethal dose for both participants will be reached in approximately four minutes

@AleCx04 Actually, it's the inline styles on a page that promotes a fucking CSS framework. Hilarious. And of course the litter of presentational classes as if we were still in the 1990s, basically abusing CSS to keep the same bad old ways from before we had CSS.

But that's the same for every CSS framework, and that's why they are bad ideas born out of gross misunderstanding what HTML and CSS even is.

Span can be quite good. I like to use it when I have single expressions that are not in the main language of the document, such as foreign words or proper terms. Then I will mark up which language that is so that screenreaders will read it properly.

Tailwind is just an excuse not to learn CSS properly. I don't really see better use cases for it than beginner projects and simple 5 page presentation websites.
For anything more complex, it is HELL to maintain (imagine having to change a specific look of 2 heavily used components, oh man). Oh you can use @apply to combine classes into a custom class? Yes, I can do that already. It is called using CSS.

I have to admit that I understand CSS better after using tailwind on side projects