re: Is the Tailwind approach a big step forward for CSS or just-yet-another-thing? VIEW POST

re: Here's my two cents (rounded to a nickel since Canadian pennies are no more...): Tailwind is super useful as opposed to a lot of other frameworks,...

This is a pretty balanced take on it.

I agree with this especially: To me, SASS is the future of CSS, but Tailwind means you can write less Sass, especially for reusable things.

I think the way forward would be to write high-level SASS mixins (say, 'content-column') on top of low-level ones (say 'content-margin' and 'body-text'), and then once some of the high-level ones are used widely across an app, you could promote them to utilities like Tailwind's.

This would give you a good compromise: readable markup, centralized rules, a separation between component and utility, and last, it would save some duplication in the generated CSS.

code of conduct - report abuse