I understand Tailwind works and gets the job done and is probably more accessible than learning CSS, but do CSS experts also prefer it?
I understand Tailwind works and gets the job done and is probably more accessible than learning CSS, but do CSS experts also prefer it?
I lived through every CSS fad for writing "maintainable" css, and have settled on Tailwind. It doesn't limit you, you can always add normal old css files to your project if you need / want to.
But what it means is I don't end up with a `utilities.scss` of `.flex` `.block` etc etc etc, which you always do on any project. I get a full catalogue of utility classes that only get included in the generated css if I use them in my project, I don't have to think about class names, and I don't have to open a separate css file.
The only con is sometimes an absolutely ridiculous amount of utility classes on an element, but frankly scarlet...
Tailwind can be a very productive tool that feels odd at first and remains odd for elements like input fields but absolutely has its place. It comes with a fraction of the foot guns typically associated with CSS for the tiny cost of looking a bit silly at first. And this is coming from someone who loves (near) class-less CSS frameworks.