Hacker News Reader

I'm a long time material ui user and always disliked the tailwind approach of slapping classnames in a long string.

After reading the excellent article it hit me, I'm already doing the exact same :facepalm:

There is really no difference, instead of a string with classes I have a bunch of props. Time to look at tailwind again...

View on HN

As a long-time MUI user myself, I had the same "revelation" about Tailwind recently. Before MUI, I worked at a couple startups where we came up with our CSS franken-framework with homegrown utility classes.

It's just easier to do fast proto-typing with various Tailwind classes, and then refactor common sets of HTML tags with tailwind classes, they become reusable React (or Svelte) components.

Reply on news.ycombinator.com