That's a common misconception by people who never used it. The truth is you need to know CSS to use Tailwind. Just because it simplifies styling doesn't mean it simplifies the underlying technology.

[–] pupbiru@aussie.zone -1 points 1 week ago (1 children)

you need to know css to use tailwind because it’s basically style= on everything: it’s css with extra steps

[–] Lemminary@lemmy.world 2 points 1 week ago

Well, it's className on everything ;) And yes, it's literally CSS utility classes with an extra installation step that you only do once

[–] kora@sh.itjust.works 3 points 1 week ago* (last edited 1 week ago)

It shocks me to see how many programmers think such framework decisions are one-size-fits-all and jump to conclusion that such framework adoption decisions are is due to lack of skillset and experience.

There are many factors at play. You have time to build and maintain your own utility framework, please go ahead.

Two years ago, I led a team which developed a web app that generated 600 million impressions per year. We used Tailwind because we were a small team and I'd rather have my developers work on high value tasks and not maintain a style framework.

If you are an aspiring developer, know this: There are always trade-offs. Not writing pure CSS does not make you a bad developer. Not knowing system design does.

[–] dajoho@sh.itjust.works 0 points 1 week ago

This is the correct answer. Pig-headed arrogance is why this cancer of a framework exists.

[–] TrickDacy@lemmy.world -2 points 1 week ago

And they hated him because he was right.