4 ms·
I think I'm pretty good at CSS and have been using it for maybe 15 years. I find tailwind just makes my life easier. Sure, it's not perfect, but I really don't
by jonwinstanley 3y ago
I think I'm pretty good at CSS and have been using it for maybe 15 years.
I find tailwind just makes my life easier. Sure, it's not perfect, but I really don't enjoy giving every div and container it's own unique name and hoping none of the names ever clash with my colleagues unique names etc.
Also, I came to realise that websites never strictly follow the same design rules throughout. There are always exceptions. So you are constantly creating new style classes that are slight modifications of others. And keeping this all in your head is not easy.
I know a lot of people disagree and feel like tailwind is a problem, but for me I can just concentrate on making a great site rather than worrying about how a slight change to the styles inside .container might break some obscure part of my website.
- throwaway154 3y agoYou don't need to give every div and container a unique ID. Why ever do that? Many things never need their own ID. Are tons of divs and containers needed? When I find myself needing containers I usually find out I've not been thinking about arrangement very well.
- llamaimperative 3y agoIf the options are "never encounter a problem" versus "when I encounter a problem I realize that it's actually a superficial symptom of a more substantial problem someone made hours/days/weeks/months ago," I will take the former 100% of the time.
- throwaway154 3y agoAssigning an ID to every single element means never encountering a problem? I imagine that results in everything being a special case, much of the point of CSS missed, and in this special case Tailwind might even work as it's consistent with everything being a mess.
- ethanbond 3y agoWell it certainly means never encountering odd and complex style cascades, but Tailwind avoids that problem altogether without requiring IDs for everything.