Disclaimer: All the words are only representing my opinions. None of them applies to the Windi CSS’s author nor the team.
Congrats Tailwind, and thanks for NOT mentioning Windi CSS at all for your new ideas.— Anthony Fu (@antfu7) March 15, 2021
I appreciated how did Tailwind power my apps and make my life easier. But this really changed my mind about how I see the people behind it.
Check out https://t.co/kcEzm5Ickp by @satireven. https://t.co/tkJCy8Pgb3
I spoke out for Windi CSS just because keeping silence on this also means we are encouraging such things to happen again in the open-source community.
Tailwind was once my favorite CSS framework and I was really happy to see we made it works on Vite much faster with @voorjaar’s astonishing Windi CSS compiler. But I was totally unexpected to see that end up being like this. Don’t get me wrong, it’s great to see Tailwind’s long pain get solved officially with Tailwind JIT and benefit the community. What I am saying is that Tailwind used/inspired by Windi’s idea without even mentioning Windi CSS once and claiming it’s their own ideas (until 20min after my tweets about that, they appended two tweets in the comments, mentioned about Windi but still implies it’s their idea. That’s all we got). No official reply of this whole thing, not updates to their repo’s README, at all.
I don’t want to speculate what’s the reasons or motivations behind it, all I know is that I will not use any products from Tailwind Labs anymore. If you think I was reacting too much or it was not a big deal, then I truly wish such things would never happend on you once again.
I remember the day when Windi got blown up on Twitter, @adamwathan called me and asked me about how Windi CSS works and he is happy to make it official. And yeah, I was excited to see things are improving for the whole community, so I shared all I know with him.— Anthony Fu (@antfu7) March 15, 2021
It's almost impossible for a small org like us to fight with the giant Tailwind. But we will not give up just because of this.— Anthony Fu (@antfu7) March 15, 2021
Let's see and good luck.
On the bright side, Windi pushed Tailwind to make the JIT and improved the DX and Tailwind forced Windi to be independent and evolving to not being a "Tailwind accessory" any longer.
There is another community based CSS-in-JS alternative called Twind, which you definitely want to check out (they are working closely with Windi to bring an uniformed community standard/spec of our DSL, cheers @sastan!).
As for myself, I will spend more time on working with Windi CSS to make it even better. Here is some of exciting things we are working on:
Spoiler of the new piece of our playground - interactive selector.— Anthony Fu (@antfu7) March 16, 2021
I always find myself trouble picking the directions of rounded corners and looking up for a huge table of all the possible combinations could be inefficient. So yeah :)
rounded-1/2 is new in Windi CSS btw 😉 https://t.co/f841k9BgPF pic.twitter.com/pVIlB2X1nY
Limitation? Let's break it!💥— Anthony Fu (@antfu7) March 17, 2021
Upcoming feature in @windi_css 🍃
"Design in DevTools"!
Whenever you made changes to the classes in DevTools, the CSS updates automatically for you, on-demand as always :)
Idea credit goes to @maximomussini 🙌 pic.twitter.com/DHf2h5wroM
Thanks for reading though. Don’t feel any pressure about using any tools that you needed. I choose not to use them just because my personal preference. I don’t want to force anyone to switch their stack because reading this post, we will keep improve it and show you which is the better one you should use :)