idk if nesting is the reason people used tailwind. imo it's more that css itself is a lot of complexity and overhead to write if you already have nesting and reuse in whatever you're using to produce html, ex react. I'd rather not have to maintain a css tree and a component tree when it can all be colocated.

writing raw html? yeah tw doesn't make any sense

[–] GTG3000@programming.dev 2 points 1 week ago (1 children)

Well, I meant the opposite - in CSS you can make the styles cleaner with nesting and such. TW always ends up with a ton of copy-pasting.

Though I will be fair, I don't think the projects I've seen it in used the themes properly.

[–] brian@programming.dev 1 points 6 days ago

if you're copypasting you're not using the code reuse tools of your component library. the nesting in normal css is component nesting with tailwind. and if you're copypasting things that aren't just the same component styles but something else shared, it's just a string you can stick it in a variable.