Google AI Studio is now sponsoring Tailwind CSS

Post by maxloh » Fri, Jan 09, 2026, 3:05 AM UTC

ricardobeat wrote: post #104

mdasen wrote: post #14

This is good, but it doesn't necessarily mean that Tailwind is out of the financial difficulty that we talked about yesterday. You can sponsor Tailwind for as little as $6,000/year. 29 companies were already sponsoring Tailwind including 16 companies at the $60,000/year level. Maybe Google AI Studio has decided to shell out a lot more, but it could also be a relatively small sponsorship compared to the $1.1M in spons…

No ill will towards the team, but isn’t it almost absurd that a CSS library is funded to the tune of 1m+ yearly and is still in financial difficulty? It is technically complete. There is no major research work or churn like in React, no monstruous complexity like Webpack.

Post by jeremyjh » Fri, Jan 09, 2026, 3:14 AM UTC

bodge5000 wrote: post #160

There are a lot of comments to the tune of "why does a CSS library need 1m+ (or any money at all) to survive?". I'm no expert on this kind of thing, but Tailwind 0.1.0 first released on November 2017. Since then, there's been continual improvements up until last month with 4.1.18, totalling 8 years of dev work. A simple CSS library wouldn't have much need to go past 0.1.0, certainly not 1.0.0. Clearly tailwind did, w…

Post by sebmellen » Fri, Jan 09, 2026, 3:19 AM UTC

raincole wrote: post #187

birken wrote: post #111

Earlier quoted context omitted.

What kind of headcount do you estimate $1MM/year can reliably support? That's like ~2 engineers at FAANG.

Blender pays their developers ~ $3M/year. [0] I'm having a very hard time to believe you need one third of that to maintain a library that does "shorter names for standard CSS." Of course I might be underestimating Tailwind a lot. [0] https://download.blender.org/foundation/Blender-Foundation-A... [1] But given the unit is euro in this report, I guess the solution is to not hire developers in the US.

Post by Maxious » Fri, Jan 09, 2026, 3:46 AM UTC

shit_game wrote: post #170

ricardobeat wrote: post #104

Earlier quoted context omitted.

No ill will towards the team, but isn’t it almost absurd that a CSS library is funded to the tune of 1m+ yearly and is still in financial difficulty? It is technically complete. There is no major research work or churn like in React, no monstruous complexity like Webpack.

I'd imagine that infrastructure costs are rather significant for Tailwind, and that there are non-neglibible organizational costs as well.

Post by runako » Fri, Jan 09, 2026, 3:56 AM UTC

ericmcer wrote: post #127

ricardobeat wrote: post #104

Earlier quoted context omitted.

No ill will towards the team, but isn’t it almost absurd that a CSS library is funded to the tune of 1m+ yearly and is still in financial difficulty? It is technically complete. There is no major research work or churn like in React, no monstruous complexity like Webpack.

Having worked on design system teams before people can burn a lot of time and money doing overly nuanced stuff. I have been in meetings discussing removing/adding a property on a React component before. That said 3 motivated developers and a designer should be more than sufficient to build a css library, but you could 100% have a team of 20 and they would find stuff to do.