It's just inline styles with extra steps. I know it seems a bit lazy to rehash other users criticisms of inline styles to explain what's wrong with Tailwind, but it really is a 1-to-1 mapping. Or LogRocket: Why you shouldnвЂ™t use inline styling in production React apps. Or StackOverflow: What's so bad about inline CSS?. For example: Lifewire: Avoiding Inline Styles for CSS Design. So - with that in mind, with the exception of CSS prioritization, any argument you could make against using inline styles in your codebase is also an argument against using Tailwind. Well - slightly different in that inline styles have higher priority than classes, but that's not really relevant in this context. Writing foo has the same exact effect as writing foo. This is just inline styles with extra steps. What Tailwind does is take that concept to the extreme, with the idea being that you almost never have to write CSS, you just write different classes based on what styles you need to apply. I have written, and used utility classes a great deal myself, especially when I'm writing CSS without the aid of CSS-in-JS solutions or a preprocessor like Sass/SCSS. Then, in every component that needs to be flexed, you add that 'flex' class. Enter fullscreen mode Exit fullscreen mode

Inherit font looks awful on chrome