News for hackers. Stuff that matters.
Re:Tailwind Is a Leaky Abstraction by nailer on Tuesday November 29, 2022 @10:54AM (#33789098)
> How does Tailwind require bouncing between multiple files?

You have styling split between the classes and the actual CSS tailwind implements, which every team I know that has used tailwind absolutely does have to look at.

Re:Tailwind Is a Leaky Abstraction by christophilus on Tuesday November 29, 2022 @12:54PM (#33790819)
It's a vocabulary you quickly get used to, and when paired with editor plugins, it's a non-issue in my experience.
Re:Tailwind Is a Leaky Abstraction by diob on Tuesday November 29, 2022 @01:02PM (#33790928)
Yeah, and it's much better than trying to figure out what random class names some dev made up are doing.
Re:Tailwind Is a Leaky Abstraction by nailer on Tuesday November 29, 2022 @04:38PM (#33793694)
I agree that ‘div soup’ is a problem - I’ve seen a lot of react code by new developers that resembles GWT generated DOMs. But ‘div soup’ has other problems too - way over complicated doms are hard to edit and debug - and the problem is better solved by learning CSS basics to avoid all the wrapper divs you see in React apps made by junior front end developers.
Re:Tailwind Is a Leaky Abstraction by nailer on Tuesday November 29, 2022 @04:35PM (#33793663)
Most of the time I know the CSS already I have to convert it to tailwind - and devtools uses the same syntax so (as the article mentions) the abstraction leaks.