Skip to content

Commit

Permalink
chore: update
Browse files Browse the repository at this point in the history
  • Loading branch information
antfu committed Mar 20, 2021
1 parent b8428da commit 39477df
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion pages/posts/windicss-and-tailwind-jit.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,14 @@ duration: 8min

I spoke out for [Windi CSS](https://github.com/windicss/windicss) 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](https://twitter.com/antfu7/status/1361398324587163648) with [@voorjaar](https://github.com/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](https://twitter.com/adamwathan/status/1371542711086559237?s=20), 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, nothing, at all.
Tailwind was once my favorite CSS framework and I was really happy to see we made it works on Vite [much faster](https://twitter.com/antfu7/status/1361398324587163648) with [@voorjaar](https://github.com/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](https://twitter.com/adamwathan/status/1371542711086559237?s=20), 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.

<Tweet>
<p lang="en" dir="ltr">I remember the day when Windi got blown up on Twitter, <a href="https://twitter.com/adamwathan?ref_src=twsrc%5Etfw">@adamwathan</a> 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.<br><br>1/n <a href="https://t.co/Ho1DddqA33">https://t.co/Ho1DddqA33</a></p>&mdash; Anthony Fu (@antfu7) <a href="https://twitter.com/antfu7/status/1371538602488786945?ref_src=twsrc%5Etfw">March 15, 2021</a></blockquote>
</Tweet>

<Tweet>
<p lang="en" dir="ltr">It&#39;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.<br><br>Let&#39;s see and good luck.</p>&mdash; Anthony Fu (@antfu7) <a href="https://twitter.com/antfu7/status/1371538609388494852?ref_src=twsrc%5Etfw">March 15, 2021</a>
</Tweet>
Expand Down

0 comments on commit 39477df

Please sign in to comment.