Senior front-end engineer here! I hated, HATED Tailwind for ages. It made me super angry that it was glossing over everything that makes CSS great. The ability

Senior front-end engineer here! I hated, HATED Tailwind for ages. It made me super angry that it was glossing over everything that makes CSS great. The ability to write great, maintainable styles seemed lost. But after a couple of projects using Tailwind, I actually think it's a really solid way to implement styling that scales well as a project/team grows. It's maintainable because it's tightly coupled to markup (like styled APIs), has great first class support for design tokens and once you learn the syntax it can let you express specific css rules in a way that's more clear and concise. I don't know if it'll have much staying power as the front end community continues to explore how we want to define styles. But what is clear from Tailwind's success is people want high levels of performance, styles tightly coupled to markup, a first-class way to utilise theme tokens etc. For now if I was to start a new project, I'd likely pick Tailwind unless there was a good reason not to.