WindiCSS-Is it a Tailwind CSS Killer? Review and Demo

When it was released, Tailwind CSS is of those frameworks that made everyone notice. Popularity, breeds competition and there's a contender that's been gaining ground called WindiCSS. Let's take a look at why you'd want to consider it, and then we'll build something with it.

Tailwind's utility based approach is [a bit controversial](https://adamwathan.me/css-utility-cla..., but it's perfect for today's component focused frameworks like React and Svelte. I've really grown to enjoy it.

The problem with Tailwind CSS 2 is that it has a ton of classes which will create large files unless you use the PurgeCSS option.

WindiCSS was created to solve some of these problems with a JIT compiler that is a central part of how it works. Newer versions of Tailwind introduced something called the JIT compiler to fix this, which will be a standard when version 3.0 comes out soon.

Fully compatibile with Tailwind v2.0
Zero dependencies: no PostCSS or Autoprefixer
First class integration: Vite, Rollup and it also offer it's own CLI, if you want to roll your own build process.
Condensed manual that's easier than Tailwinds
Additional Features

The newest version of TailwindCSS has one advantage and that's the CDN JIT version, which lets you build a custom css file from a CDN. That makes it easier to do demos, but it means that you're going to need a build process to try out WindiCSS. There is, however a cool online playground https://windicss.org/play.html