<story><title>Play with TailwindCSS in the Browser</title><url>https://play.tailwindcss.com</url></story><parent_chain><item><author>halotrope</author><text>There is only two kinds of people. The ones that don&amp;#x27;t like Tailwind and the ones that have used it.&lt;p&gt;I know it is conceptually &amp;quot;wrong&amp;quot; and a bunch of well crafted CSS classes would be more elegant. In the end it works, works really well and makes collaboration dead simple. Commonly used groups of classes can either be aliased by @apply or used in a (react) component. 
I used CSS way before Tailwind was a thing and in hindsight I created a lot of utility classes that resembled a weakly-structured, somewhat incomplete version of Tailwind.&lt;p&gt;It might be a bit verbose, it might be easy to abuse but it works damn well. 
On top of that there are some design guardrails built in that really help with the consistency of e.g spacing, colors and fonts. 
Easy to achieve good looking results without risking stuff always looking the same like with Bootstrap or Material.&lt;p&gt;It is a bit like Github Copilot. The only way to &amp;quot;get&amp;quot; it is to try it.</text></item></parent_chain><comment><author>erokar</author><text>I&amp;#x27;ve used Tailwind on many projects at work for about a year now. I do not like it.&lt;p&gt;Tailwind seemingly affords an easy way of writing inline styles, but it 1) clutters the HTML, 2) leads to repetition and makes people break the DRY principle (yes, you should extract to components, but people don&amp;#x27;t always do that), 3) uses names that can be similar but are not identical to CSS properties and feels like a bad abstraction.&lt;p&gt;If you use something like Svelte, where you can write local CSS within a component I fail the see the benefit of Tailwind. For me Tailwind is the most ill-conceived frontend tech I&amp;#x27;ve had to use in later years.</text></comment>
<story><title>Play with TailwindCSS in the Browser</title><url>https://play.tailwindcss.com</url></story><parent_chain><item><author>halotrope</author><text>There is only two kinds of people. The ones that don&amp;#x27;t like Tailwind and the ones that have used it.&lt;p&gt;I know it is conceptually &amp;quot;wrong&amp;quot; and a bunch of well crafted CSS classes would be more elegant. In the end it works, works really well and makes collaboration dead simple. Commonly used groups of classes can either be aliased by @apply or used in a (react) component. 
I used CSS way before Tailwind was a thing and in hindsight I created a lot of utility classes that resembled a weakly-structured, somewhat incomplete version of Tailwind.&lt;p&gt;It might be a bit verbose, it might be easy to abuse but it works damn well. 
On top of that there are some design guardrails built in that really help with the consistency of e.g spacing, colors and fonts. 
Easy to achieve good looking results without risking stuff always looking the same like with Bootstrap or Material.&lt;p&gt;It is a bit like Github Copilot. The only way to &amp;quot;get&amp;quot; it is to try it.</text></item></parent_chain><comment><author>kanonieer</author><text>&amp;gt; There is only two kinds of people. The ones that don&amp;#x27;t like Tailwind and the ones that have used it.&lt;p&gt;I know a lot of people who have tried but didn&amp;#x27;t like Tailwind. I think most people like it on a greenfield project, but that number drops off when they go back to a Tailwind project after some time.</text></comment>