Front end developer specialising in JavaScript and React. Experienced in all aspects of modern front end development. Passionate about making accessible, secure and performant software.
To answer the question: I think Tailwind is here to stay. I put it in the same boat as other CSS frameworks like Bootstrap and Bulma.
It has a good advantage because its styles are quite specific and utility-like, which allows us to style things any way we want. In comparison, something like Bootstrap provides classes for components and not many utility classes. To modify components further, we need to write our own CSS. Of course the downside of Tailwind CSS is that because each class provides less styles, we need more of them in our HTML.
So it has pros and cons, as with anything, but it's a great option to have. It's my preferred choice for a CSS framework.
However, I still strongly believe that something like BEM is more suitable for larger projects that value scalability, robustness and pixel-perfect designs.
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.
To answer the question: I think Tailwind is here to stay. I put it in the same boat as other CSS frameworks like Bootstrap and Bulma.
It has a good advantage because its styles are quite specific and utility-like, which allows us to style things any way we want. In comparison, something like Bootstrap provides classes for components and not many utility classes. To modify components further, we need to write our own CSS. Of course the downside of Tailwind CSS is that because each class provides less styles, we need more of them in our HTML.
So it has pros and cons, as with anything, but it's a great option to have. It's my preferred choice for a CSS framework.
However, I still strongly believe that something like BEM is more suitable for larger projects that value scalability, robustness and pixel-perfect designs.