I agree with css being a low level, powerful, ultimate, but last resource to do styling. Today's component frameworks like React has change the way you build user interfaces, and plain css or scss with post processors are not the best match for components. There are new and better ways like combining the power of utility classes with all the benefits you gain with css-in-js. A tool like twing.macro allow you to perfectly mix the beautiful tailwindcss utility classes, with styled-components, emotion, or goober. With these you can open a whole new means to style fast and efficiently.
My point is, in my projects I always try to write as few plain, repetitive css as posible, I really prefer using tailwindcss paired with css-in-js paradigm that allows me to organize much better and choose the best alternative for each case.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I agree with css being a low level, powerful, ultimate, but last resource to do styling. Today's component frameworks like React has change the way you build user interfaces, and plain css or scss with post processors are not the best match for components. There are new and better ways like combining the power of utility classes with all the benefits you gain with css-in-js. A tool like twing.macro allow you to perfectly mix the beautiful tailwindcss utility classes, with styled-components, emotion, or goober. With these you can open a whole new means to style fast and efficiently.
My point is, in my projects I always try to write as few plain, repetitive css as posible, I really prefer using tailwindcss paired with css-in-js paradigm that allows me to organize much better and choose the best alternative for each case.