I was skeptical. Do we really need another version of Tailwind? After using v4 for a client project, the answer is a resounding yes.
The Zero-Config Revolution
Gone are the days of the 500-line tailwind.config.js file. Version 4 automatically detects your project structure and applies intelligent defaults. It feels less like "configuring a framework" and more like "just writing CSS."
Performance Benchmarks
We benchmarked a large e-commerce dashboard build times:
- Tailwind v3: 4.2 seconds (Webpack)
- Tailwind v4: 0.8 seconds (Vite + Lightning CSS)
This speed difference changes how you work. You stop hesitating to save the file. The feedback loop is instant.
Modern Variable Handling
The new @theme directive allows us to define variables directly in CSS, but with the power of Tailwind's scale system.
@theme {
--color-primary: #3b82f6;
--font-display: "Satoshi", sans-serif;
}
This bridges the gap between traditional CSS variables and Tailwind's utility classes, making it easier to integrate with third-party libraries that expect standard CSS properties.