tailwind is trash holy crap.

every div element contains like 30 classes that have their own thing going for them.

just start writing inline css at that point. Why bother putting classes in?

If you thought Tailwind was bad, I've worked with popular CSS libraries that were hell on earth... with tons of their own randomized, restrictive classes as well.

Why not write in inline styles? Well, the answer depends: maintainability/traceability.

I've made a few projects with tailwind and i've been a big fan. But most of the HTML semantic tags really lost their use over the years or a lot of webdevs ignores them

CSS is retarded. Nobody needs it.

@antigermgerm

apparently some people like to choke on it's dick

@wojtek322 Semantic tags are arbitrary and reeks of makework nonsense inserted by non-developers.

Utility classes can be really nice

.text-center .no-select .text-muted .text-bold

I think I draw the line when we’re doing this:

.d-flex.align-items-center.justify-content-center

Define a single class that does all of that! Don’t write inline CSS and use utility classes as an excuse!

Somebody accused them of having no class. They took it literally.

classless frameworks is all you need.

@whimsical I used to love bulma because of that, but now I see they have

<button class="button">Button</button>

🤮