I simply don't see the point of tailwindcss. If you want to put your styling on each element in your HTML, just use the style attribute.
The secret of tailwindcss is that you'll think that it is a really bad idea until you start using it. About using the style attribute, is super different. Here are some reasons:
But again, give it a try and you will thank me later 😄
Check out this link: 2019.stateofcss.com/technologies/c...
TailwindCSS is leading the ranking both on interest and user satisfaction on 2019.
No thanks. I'd rather keep my separation of concerns and my styling completely out of my markup. But thanks for responding.
In case you are interested in the argument for utility-first css (especially regarding separation of concerns) this article by the tailwind author really made it click for me:
The general case for utility first is nicely made in the tailwind docs:
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.