3 ms·
Looked into tailwind 2-3 times and simply couldn't see the appeal. Working on analytical-dashboards in react, I mostly end up writing css straight in js using m
by Bishonen88 6y ago
Looked into tailwind 2-3 times and simply couldn't see the appeal. Working on analytical-dashboards in react, I mostly end up writing css straight in js using material-ui's makestyles. There's only so many components to style before I start reusing them and the css needed to make something 'not-look-too-crappy' is actually quite low.
Now after learning all the css basics, I'd have to learn yet another 'system' again? I think I'll pass.
On the other hand if I'd be constantly restyling webpages with hundreds of different components etc., I might consider it again...
- joshpadnick 6y agoWhat you're missing is that there's overhead in writing CSS-in-JS. You have to switch context from HTML to JS, you have to keep track of the "link" between your CSS-in-JS and your React component, you have to deal with cascading styles, and hopefully you're able to keep all styles across all components consistent. Tailwind cuts through all of that and says: - Just declare the styles you want directly in the HTML - If you're repeating styles, use @apply - Limit the number of styles available to your project to enforce a de facto design system
- mikewhy 6y agoMaterial UI still fulfills all those points, unless I'm missing something: - Just declare the styles you want adjacent to the component - If you're repeating styles, make a component - material-ui has a design system / theme that you're encouraged to use Like Tailwind has `class="mb-6"`, mui has `<Box mb={6} />`.