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.
Typescript is delightful to ensure that everything works and you don’t get surprises. Tailwind though…
…it’s certainly faster in the development but it’s not nearly as nice as CSS can be, especially since now any browser supports nesting.
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
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.