Adam Wathan at Rails World - Tailwind CSS: It looks awful, and it works

Laravel News

Adam Wathan explains why 'separation of concerns' isn't the right way to think about the relationship between HTML and CSS. He also shares tips, tricks, and best practices for using Tailwind CSS effectively.

Tailwind CSS: It looks awful, and it works

<p>If we are talking about the finished product. If it looks awful in Tailwind.css, it would look awful using anything because that’s a developer issue not a Tailwind.css issue. Nothing that you can do with CSS isn’t possible with Tailwind, it just makes the whole process a little more seamless especially in a components based framework where you are including the JSX in the JS (or whatever) as it enables atomic design of your components without that meaning the onerous and awful additional <code>.module.css</code> file but instead some classes that can include arbitrary values and loans itself to customization to a depth often wholly unexplored by its detractors.</p>
<p>If we are talking about the code itself, that’s meaningless given preferences on the appearance of code are wide and wild but constrained to each person’s idiosyncratic quirks. Some people think lisp (that nightmare from emacs configuration) looks good. Others think [insert anything] looks better and some require syntax highlighting to think any of it looks good or make any sense of it at all. For the same reason, some people like coffee, others like tea and on the fringe are weirdos like me with yerba matte mixed with lemon juice and fresh mint I grow on the window seal. Its arbitrary and unimportant, at the end of the day we are all caffeinated and have higher blood pressure.</p>
