3 ms·
Clearly there are lots of people who love Tailwind, but for me it really misses the mark. Yes, it's extremely ugly and unreadable when you have 10-20 classes.
by lawn 3y ago
Clearly there are lots of people who love Tailwind, but for me it really misses the mark.
Yes, it's extremely ugly and unreadable when you have 10-20 classes.
But worse, you have to repeat them in other components even if you only want to change a single one of them. And making changes to multiple components, good luck.
Thanks but no thanks. I'll continue with my systems designed in css and sass.
- akiselev 3y agoI use a vscode extension [1] to fold all CSS classes. Really helps to clean up the ugliness when I'm not focused on styling. For components, I move the class names to an @apply directive in a css rule [1] https://marketplace.visualstudio.com/items?itemName=stivo.tailwind-fold https://marketplace.visualstudio.com/items?itemName=stivo.ta...
- burlesona 3y agoTailwind 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.
- diob 3y agoI 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}`} />
- kebsup 3y agoYou can still use global styles with tailwind. After you style components like buttons, inputs and cards globally, I've found surprisingly low amount of repetition.