this post was submitted on 04 Feb 2025
36 points (92.9% liked)
Programming Circlejerk
159 readers
8 users here now
Community to talk about enlightened programming takes
Rules:
- read and follow the programming.dev code of conduct
- no flamewars
- mark your unjerks
- only programming related content allowed
- link to the original source
- do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.
founded 2 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.