www.youtube.com
Tailwind CSS is the worst…
Excerpt
{ts:104} Blasphemous inline Styles at first glance and that's a very valid criticism {ts:108} and likely the main turn off for people {ts:110} when they first look into using Tailwind however the benefit is that you don't {ts:113} have all these arbitrary class names … {ts:126} tailwind and hate the way your HTML looks the inline fold vs code extension {ts:129} can automatically minimize it for you {ts:131} problem number two is that CSS is for Bose remember everything in Tailwind is {ts:135} just CSS hover over any class to view … {ts:160} you have to learn an abstraction on top of CSS which is not ideal it's always {ts:164} best to use the platform natively but {ts:166} the web platform is often cruel and vengeful Now problem three is that CSS {ts:170} gives you too much control over the UI … {ts:182} design like when you build a bootstrap app it always tends to look like a {ts:185} bootstrap app with Tailwind is not so {ts:187} obvious now the final problem I want to talk about is zombie Styles we have a {ts:191} tendency to write styles that never
Related Pain Points
Loss of fundamental CSS knowledge among developers
6Developers using Tailwind are abstracting away core CSS knowledge (Flexbox, Grid, positioning). Junior developers can use Tailwind classes but don't understand the underlying CSS properties, creating a generation gap in web platform fundamentals.
Separation of concerns violated by mixing styles with markup
3Tailwind mixes CSS styling concerns directly into HTML markup, violating traditional separation of concerns principles and resulting in code that looks like inline styles, which many developers find aesthetically unpleasant.