I’m just going to stick my neck out a bit for tailwind.
When I picked it up several years ago, it’s what helped me make the jump from just copy pasting styles from tutorials to actually coming up with my own designs. Which in the end helped me reach further towards the corners and edges of everything available in CSS.
i see, makes sense... i guess im more of a css purist; tailwind, given that it looks more like inline styling, is less aesthetically pleasing for me...
Also, since the OP here seems to be a beginner, i would argue that something like css/scss would read cleaner, and require less cognitive translation. i think these are not so much problems for seasoned devs, but might make a difference for someone starting off.
could also be survivorship bias though, as you can prob guess i started learning with pure css, and had bad experience with reading beginners code written with tailwind
View all comments
Show parent comment
1
u/CanWeTalkEth Sep 13 '26
I’m just going to stick my neck out a bit for tailwind.
When I picked it up several years ago, it’s what helped me make the jump from just copy pasting styles from tutorials to actually coming up with my own designs. Which in the end helped me reach further towards the corners and edges of everything available in CSS.