What working with Tailwind CSS every day for 2 years looks like

Re:What working with Tailwind CSS every day for 2 years look... by johnchristopher on Tuesday November 29, 2022 @12:00PM (#33790096)

> This plugin would allow me to use my existing CSS knowledge by writing:

   <div
     class="display-flex align-items-center gap-8px border-radius-6px padding-4px"  
    >
    <!-- ... -->
    </div>

> Instead of:

    <div class="flex items-center gap-2 rounded-full p-1">
      <!-- ... -->
    </div>

But... why ?

I just don't get tailwind.

[ Parent | on HN ]

Re:What working with Tailwind CSS every day for 2 years look... by themosaad on Tuesday November 29, 2022 @05:04PM (#33794022)

This is far from being the best example of WHY you should use Tailwind CSS. I wrote about the HOW.

I'll try to write another article about the WHY soon.

[ Parent | on HN ]

Re:What working with Tailwind CSS every day for 2 years look... by johnchristopher on Wednesday November 30, 2022 @12:41AM (#33797394)

I think something clicked yesterday after reading a comment. It works for SPA/css-in-js/components-based projects, and this long class string is manageable as long as it is only present in one single place in the whole project (thinking about versioning and the mental model of where's what).

[ Parent | on HN ]

Re:What working with Tailwind CSS every day for 2 years look... by esparrohack on Tuesday November 29, 2022 @10:25PM (#33796653)

My gripe is that it’s stuff I don’t always have to care about. If I’m not working with CSS it’s just noise.

Whatever way that’s refactored, I only want to see that when I’m working with the styles and I don’t wanna do anything special for it either.

[ Parent | on HN ]