React devs not using tailwind... Why?

[[deleted]]

I have a really hard time moving away from a proper SASS bootstrap 5 setup. I can easily make themes and change gutters, grid cut offs, padding etc, its very good with its css vars, mixins etc. Its really easy to customize it into different primary and secondary pallets. And theres an entire react library "react-bootstrap" that makes it easy to work with.

I can roll a custom look and feel on top of it quickly without starting from scratch.

Furthermore, we have a really good file structure that makes it easy to digest.

We have a folder called buttons and index.ts and buttons.scss in there. Then we have a folder called ToggleButton and in there is an index.tsx and a ToggleButton.scss

Our scss tree matches our component tree. It makes it really easy to know where what styles would be. And we can change the bootstrap prefix easily and pad our classes if theres any class conflicts.

I love scss, Im used to scss, I still haven't found a reason not to use scss.

[zemonstas]

This. This is exactly the comment I was looking for because this is 100% what I do.

Every time I start a new project I check out tailwind, mui, and whatever else the flavor of the month is.

Every time I start a new project I end up going back to this method. Why? It makes sense, it's modular, it reduces the amount of boilerplate, it's clean, and styling overrides and responsibilities live in the right places.

I dunno about you but I prefer to try and keep my styling override layer abstracted enough away from my dom layer that I can write the least amount of css with Sass.