News for hackers. Stuff that matters.

A comment on Why Tailwind CSS Won. Parent comment

Re:Why Tailwind CSS Won by throwaway154 on Wednesday August 16, 2023 @10:29AM (#37147605)
You 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.

[ Parent | on HN ]
Re:Why Tailwind CSS Won by ethanbond on Wednesday August 16, 2023 @10:32AM (#37147655)
If 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.
[ Parent | on HN ]
Re:Why Tailwind CSS Won by throwaway154 on Wednesday August 16, 2023 @11:07AM (#37148249)
Assigning 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.
[ Parent | on HN ]
Re:Why Tailwind CSS Won by ethanbond on Wednesday August 16, 2023 @11:19AM (#37148446)
Well it certainly means never encountering odd and complex style cascades, but Tailwind avoids that problem altogether without requiring IDs for everything.
[ Parent | on HN ]