3 ms·
I see tailwind as a new form of CSS built for the component age. It’s not a framework or design system.
by teaearlgraycold 2y ago
I see tailwind as a new form of CSS built for the component age. It’s not a framework or design system.
- sodapopcan 2y agoYes! This sums it up perfectly. To the latter point, it's more so a tool for building design systems that comes with a [very large and thorough] default implementation.
- conradludgate 2y agoI prefer scoped css, eg svelte or react with CSS modules. This allows one to closely pair the styles with the component, but still separate out the styling from the html (I cannot stand tailwind/inline syles)
- foretop_yardarm 2y agoMy favourite way too and fwiw not mutually exclusive with Tailwind (in case anyone was wondering).
- teaearlgraycold 2y agoSometimes it’s necessary when using tailwind (I often use traditional CSS for animations). What’s the hip way to have CSS specific to a component? I remember StyledComponents from years ago. I wasn’t as much into front end then.
- tuzemec 2y agoI see it as a way of granular styling, because there's no cascading. And IMO works great if you style each element (or component) individually. But the moment you need to style real html and not some kind of component structure - you have to look for something else. If I switch to "old man yelling at the sky" mode I would say that's an example of a nice concept (utility classes) taken way too far.