On: Ask HN: Am I Misunderstanding TailwindCSS?

No, you’re not missing anything. Tailwind is a disastrous anti-pattern that the whole web dev community should be fighting against. (Web dev here since ‘96.)

I could not second this more. Tailwind is a member of a category of CSS frameworks which dramatically implement anti-pattern. Another example of this category is https://semantic-ui.com/.

The only way I see how to use these libraries while maintaining a clean seperation of content and style is to use some CSS generator (LESS, SASS) and setup custom classes inheriting styles from tailwind et al.

I had heard the hype for a while and was excited when I found out I was starting on a new project that was using tailwind. My excitement quickly turned to shock when I saw how much of an utter mess tailwind makes. Antipattern is exactly they way I would describe it as well.

I'll write old school scss over tailwind any day.

My favorite toolset is:

  - vue3 + typescript
  - scss
  - bulma ( https://bulma.io )
  - https://coolors.co/ to create color palettes

I've also worked with the Quasar Framework ( https://quasar.dev ), which gives you a lot out of the box, but I love the simplicity of vue3 on its own.

Can you explain why?

Someone needs to create a sexy marketing video showing how easy it is to style a card using plain css :)

But how do we sell CSS?