These are all great points! I especially like 8 & 14 :)
About 4 & 5: isn't Tailwind CSS just another Bootstrap? Useful for people who don't want or don't know how to write CSS, and want to build an interface quickly? If so, it probably means devs like me will never use it, but hey... if it helps you build that cool startup app while staying sane, I say go for it.
I'm often wrong about trends but I don't believe the hype on this one; and if it does become the de facto way of building UI, then... damn!
I don't believe that comparison is fair. The commercial service called Tailwind UI would be a closer match. Utility classes is a different way of working with CSS, and it very much requires CSS knowledge to use it in any meaningful way.
Several other frameworks are built on the same utility principles, but they are lacking some efforts to gain the success Tailwind CSS has achieved. I think that comes down to a mix of things. Marketing, good documentation, choosing the "right technology" to build the framework, research and careful decision making, and a lot of hard work.
That exact framework is promoting a utility-first approach, but I think a lot of people read it as utility-only. Mixing is ok. If someone choose to use that framework, they should think critically about the default configuration, and take steps to change what is useful for their project
Working with a utility classes framework isn't for everyone, and that is very ok :)
These are all great points! I especially like 8 & 14 :)
About 4 & 5: isn't Tailwind CSS just another Bootstrap? Useful for people who don't want or don't know how to write CSS, and want to build an interface quickly? If so, it probably means devs like me will never use it, but hey... if it helps you build that cool startup app while staying sane, I say go for it.
I'm often wrong about trends but I don't believe the hype on this one; and if it does become the de facto way of building UI, then... damn!
I don't believe that comparison is fair. The commercial service called Tailwind UI would be a closer match. Utility classes is a different way of working with CSS, and it very much requires CSS knowledge to use it in any meaningful way.
Several other frameworks are built on the same utility principles, but they are lacking some efforts to gain the success Tailwind CSS has achieved. I think that comes down to a mix of things. Marketing, good documentation, choosing the "right technology" to build the framework, research and careful decision making, and a lot of hard work.
That exact framework is promoting a utility-first approach, but I think a lot of people read it as utility-only. Mixing is ok. If someone choose to use that framework, they should think critically about the default configuration, and take steps to change what is useful for their project
Working with a utility classes framework isn't for everyone, and that is very ok :)
You're right. I haven't used it yet, and I'm warming up to the idea of going "utility-first" so I should do my homework before complaining about it!
Like I said, if it makes website development easier (to get into, to maintain projects, etc.), it's a win in my book.