Tailwind and the Beauty of Ugly Code
As someone who is skeptical about Tailwind because I&#x27;ve learnt to separate the structure from the presentation (the old school way).<p>It reads like the advantages listed in the article would apply if one used style=&quot;....&quot; everywhere. Which does not sell it well to me. Then again the author says they needed to actually try Tailwind for it to &quot;click&quot;. But then again, they are praising something without much long term insight, I&#x27;d be interested to have an opinion from someone who has maintained a project for one or two years, or more.<p>Tailwind feels like Bootstrap to me: as someone who has written raw CSS for years, you need to learn a new vocabulary and map it to standard CSS. Which I don&#x27;t feel the need for. I know CSS, and you kind of have to anyway even when using a CSS framework. With the extra disadvantage that you need to have a build pass so Tailwind can pick up the dynamic classes you used to build the corresponding CSS for you. But I really want to write this CSS myself and have meaningful class names, I feel like it helps me understand what&#x27;s what when working on the structure. I can always inspect with the web developer tools if I want do understand what styles apply.<p>I see the appeal of having some default design system applied to your thing and not having to write some style reset stuff when using a CSS framework like Bootstrap, but even for this I&#x27;m not sure about the benefit&#x2F;drawback ratio. I work for a company whose product is somewhat trapped in an old version of bootstrap because it can be augmented with extensions, and not the old bootstrap version is part of the API, if you update it you break the API.<p>I don&#x27;t know.