Great article! Thank you.
I also think, it heavily depends on the complexity of the projects and how you structure your code. The idea of having your styles and markup at the same place is very intriguing.
However, one downside you forgot to mention, is the readability of your markup. Yes, you can quickly grasp what the code does but you can't really understand the semantics of the code. That's probably okay for small projects but for me personally, I prefer to write down some class names and CSS components (BEM or CUBE or whatever) so I can still understand the meaning of the markup 5 years from now.
Of course, it totally depends on your personal taste and experience. But if I speak for myself I'm glad not everybody who designs websites uses Tailwind ;)
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.
Great article! Thank you.
I also think, it heavily depends on the complexity of the projects and how you structure your code. The idea of having your styles and markup at the same place is very intriguing.
However, one downside you forgot to mention, is the readability of your markup. Yes, you can quickly grasp what the code does but you can't really understand the semantics of the code. That's probably okay for small projects but for me personally, I prefer to write down some class names and CSS components (BEM or CUBE or whatever) so I can still understand the meaning of the markup 5 years from now.
Of course, it totally depends on your personal taste and experience. But if I speak for myself I'm glad not everybody who designs websites uses Tailwind ;)