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: tailwindcss.com/docs/utility-first
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
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.
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:
tailwindcss.com/docs/utility-first