Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Tailwind makes a lot of sense for people who are doing componentized UI frameworks where they never write the same markup twice. But if you're actually writing markup in the more "traditional way" where you repeatedly mark semantic elements with classes in order to make them have a certain look and feel (and let CSS do the heavy lifting) then Tailwind is a mess.

In my experience that distinction is the most of the difference between enjoying Tailwind and not.



I don't get the reasoning, you could do the same with Tailwind, just make a mega class with all your "css". Nobody says you can't, although personally I don't do this.

<div className={`${variableWithMultipleTailwindClasses}`} />




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: