Adam Wathan, one of the creators of Tailwind, wrote about his transition away from writing "conventional" CSS when he started the project: https://adamwathan.me

Adam Wathan, one of the creators of Tailwind, wrote about his transition away from writing "conventional" CSS when he started the project: https://adamwathan.me/css-utility-classes-and-separation-of-concerns/ https://adamwathan.me/css-utility-classes-and-separation-of-... The Tailwind docs also cover a lot of your questions: https://tailwindcss.com/docs/utility-first https://tailwindcss.com/docs/utility-first From my point of view, I made the same realisation as Adam and found Tailwind suits my needs very well. Learning and using only the classes provided by Tailwind is actually very freeing and helps me rapidly build out a design. I've also found projects built with Tailwind to be very maintainable. However, if you don't feel like Tailwind is right for you then don't feel any pressure to use it, regardless of how many people sing its praises.