Tailwind: style your site without writing any CSS
How would have React adoption looked like if it wasn&#x27;t backed by a tech giant? React propounds a very controversial idea: to put HTML inside Javascript. Of course, once you get the hang of it, it all makes perfect sense: tight coupling and composability.<p>Tailwind, along the same lines, proposes a contrarian idea and it will only make sense once you start working with it. Here&#x27;s what I have seen happen frequently: As the CSS grows, so does the bloat and repetitiveness of the same basic style. Let&#x27;s say you want to position elements in the center of a component? &quot;display: flex, align-items: center&quot; easy. But what do you do when you encounter that same requirement again? Creating a utility class and replacing existing once will be a pain, so you add the same styles again. And that&#x27;s how folks you end up with a megabyte of CSS doing a job that could be done in &lt;100Kb.<p>This pattern is more pervasive than you think. The fundamental problem is that we are not thinking about styling in terms of composability of basic styles.<p>The benefits of utility classes outweigh the cons. You can iterate faster, you don&#x27;t have to fight the framework, you don&#x27;t have rethink abstractions at every point (&quot;this style belongs to a component or a utility class&quot;) and as CSS becomes more expressive you&#x27;ll need fewer classes anyways. I hope Tailwind takes off because styling definitely needs to be less painful than it&#x27;s today.