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.

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

[JohnSmith-zlrz]

Nice but I don't want mess to much and mix both, I prefer stay clean with just tailwind, I'm sure tailwind team already see what Windi offer and they will do the same or better

[johndaveomandam]

Try Unocss from the creator of windicss

[jenstornell]

I like what I see but because Tailwind is the original and has funding I'll stick with it for now. Feels like lower risk.

[BneiAnusim]

The issue with bootstrap is that your site looks VERY BOOTSTRAPY! Anyone can tell! 😉

[pergollubits]

I'd rather just write inline css 🤣