AI summary by TwinMind
Is Tailwind really the right default?
Theo - t3․gg
22m 26s
Tailwind CSS Market Dominance
- Every AI tool leans on Tailwind CSS for styling
- Nobody forcing CSS-in-JS anymore, Tailwind "just works" for email because it's all classes
- Tailwind quickly accelerating and taking over most of style world
- Entire web ecosystem standardizing on Tailwind
- 95% of people find it as good or better than previous solutions
- 5% experiencing more pain than ever due to need for custom control
Tailwind Limitations and Solutions
- Custom classes solution: write CSS directly
- Dynamic behaviors based on state: swap out class names
- Building style system: build it yourself
- Tailwind is different way of writing CSS, not alternative to it
- Many devs/projects start with React until problem arises - same pattern emerging with Tailwind
Industry Beef: Tamagi vs Vercel
- Tamagi (component library for React/React Native) vs Guo (Vercel CEO)
- Tamagi claims: "forcing CSS-in-JS for while, we're faster and fully typed"
- Accusation: Guo invested in pushing narrative to sell server components and Turbo pack
- Threat to leak internal chat about CSS-in-JS problems
- CSS-in-JS had server rendering issues among other problems
- Guo didn't invest in Tailwind to take over world - used it because made sense
Tailwind Ecosystem Adoption
- Laravel using Tailwind
- PHP world adoption surprising
- Elixir Community with Phoenix using it
- Ruby Community with Rails adopting it
- React Native Tailwind bindings led to Expo hiring community member full-time
- Project called "Native Wind" for React Native
- Resend makes it work with email
- Tailwind websites run on PHP on VPS, not Vercel/Next.js/serverless
CSS-in-JS vs Tailwind Statistics
- CSS-in-JS has more npm downloads than Tailwind
- AI tools can output great Tailwind code
- Vercel spends money on Tailwind starting years ago
- Wanted old CSS-in-JS libs out because bad on RSC (React Server Components)
- Avoid plugin system for Turbo pack
- Turbo pack didn't support Tailwind initially
Performance Benefits of Tailwind
- Flex class in CSS is one line reused instead of rewriting "display: flex" repeatedly
- Minification benefits: "flex flex-col" repeated 100 times minifies more efficiently
- Traditional CSS requires naming classes properly, often reinventing worse Tailwind
- Many developers inadvertently reinvent huge portion of Tailwind pursuing performance wins
CSS Declaration Order Benefits
- Tailwind fixes CSS gotchas like declaration order side effects
- Example: Class A (background: blue) + Class B (background: red) = always red regardless of HTML order
- Tailwind sort plugin guarantees class order matches CSS order
- Removes bugs from CSS files loading in different orders dev vs prod
- Different regions/bundling can cause CSS order issues
Naming Problem Solution
- No more naming things - huge engineering burden removed
- Common joke: "Two hard problems in programming: caching, naming things, off-by-one errors"
- Created paradigms like BEM (Block Element Modifier) to manage naming
- Tailwind eliminates need for constant naming
CSS-in-JS Evolution
- New generation rocks: Panda, StyleX, Tagui, Parui, Vanilla Extract
- Panda offers too many options (as bad as too few)
- StyleX very promising for specific use cases
- Vanilla Extract incredible for what it invented
- Next.js first tried CSS-in-JS with Glamour by Sunil Pai
Developer Experience Patterns
- Tailwind haters often become lovers after usage
- Similar to music - favorite songs often initially disliked
- Strong emotional investment when starting from hate position
- CSS-in-JS users more neutral, less likely to flip strong reactions
- Majority of Tailwind haters are potential users who haven't used enough
StyleX Positioning
- Created by Nan (Facebook/Meta)
- If Tailwind is React, StyleX is Solid
- Result of knowing deeply how everything works
- Perfect solution knowing DX can't be quite as good
- Works at Meta scale where Tailwind doesn't
- Allows writing styles that work everywhere universally by default
Default Framework Philosophy
- Good default isn't perfect for everyone
- Meets needs well enough to lean on for most things
- Tailwind allows not changing style solutions every 6 months
- Been using Tailwind since 2020 (4 years) without core changes
- Tools around Tailwind changed (clsx → Tailwind merge → CVA → shadcn/ui)
- React similar pattern - first solution good enough to stop reaching for alternatives
Future Tooling
- Nan working on Tailwind-to-StyleX compiler
- Allows using Tailwind DX while getting StyleX benefits
- Tailwind syntax consistent enough for promising conversion
- Potential future where Tailwind right starting point even if not end solution
