CEO doesn't care about your CSS strategy, as long as you use Tailwind

Re:CEO doesn't care about your CSS strategy, as long as you ... by tqkxzugoaupvwqr on Friday October 08, 2021 @11:56AM (#28800649)

Cons of using Tailwind:

- In addition to knowing CSS you now also have to learn all the Tailwind class names that map to CSS styles.

- Development starts fast because you just drop Tailwind’s utility classes into HTML elements but then you end up with a long list of classes and things become unreadable, and worse, you have to repeat yourself if you want to apply the same style to other elements. Better group the list of Tailwind classes into a custom class. Wait, we have just re-invented CSS classes but need additional build tools.

[ Parent | on HN ]

Re:CEO doesn't care about your CSS strategy, as long as you ... by phreack on Friday October 08, 2021 @12:59PM (#28801392)

I think Tailwind really shines alongside a tool like React where you don't abstract out a class of Tailwind classes, but a whole component with minimal to no functionality. If you end up with too many of those then maybe it's a sign your design language is getting too complex?

[ Parent | on HN ]