Earlier quoted context omitted.
It seems to be in Google's interest to keep Tailwind CSS afloat. Tailwind CSS is alive -> New / existing projects keep using Tailwind CSS -> more code for Gemini to train upon -> better and fancier UIs being created through Gemini -> popularity and usage of Gemini doesn't go down Of course this applies to any other LLM provider too but I guess Google saw this opportunity first.
I think it'd be better for AI and web dev if AIs generated real CSS instead. The supposed difficulty of tracking from elements to classes to rulesets is something that AIs can easily handle, and being able to change a ruleset once and have the update apply to all use sites is really good for AI-driven changes. Plus, humans and AIs won't have to wait for Tailwind to adopt new CSS features as they are added. If the AI…
Google AI Studio is now sponsoring Tailwind CSS
81–90 of 319 posts
Re: Google AI Studio is now sponsoring Tailwind CSS
#82Earlier quoted context omitted.
What costs could tailwind the OSS project have besides payroll and SaaS subs of max 20% the payroll?
Hosting, marketing, other promotional stuff (conferences, maybe other?), there are still three people on the payroll and otherwise I don't know (which was part of my point) as I've never run a business like this before myself. Oh, subscriptions to AI services... that's pricey I hear ;)
Re: Google AI Studio is now sponsoring Tailwind CSS
#83This 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…
Re: Google AI Studio is now sponsoring Tailwind CSS
#84This 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…
>Tailwind is out of the financial difficulty Tailwind is not under financial difficulty, like, at all.
With layoffs they can meet costs but that might be true if the revenue decline trend keeps going for 18 months or so.
Re: Google AI Studio is now sponsoring Tailwind CSS
#85Re: Google AI Studio is now sponsoring Tailwind CSS
#86Earlier quoted context omitted.
I think it'd be better for AI and web dev if AIs generated real CSS instead. The supposed difficulty of tracking from elements to classes to rulesets is something that AIs can easily handle, and being able to change a ruleset once and have the update apply to all use sites is really good for AI-driven changes. Plus, humans and AIs won't have to wait for Tailwind to adopt new CSS features as they are added. If the AI…
The thing is LLM generate token by token and if you have to write entire css before writing the html, the quality could be worse.
Or you could tell the LLM that while prototyping, it should define the CSS "just in time" before/after each part of the HTML, by generating inline s that embed CSS stanzas as string literals, and which immediately inject those into the document using CSSStyleSheet.insertRule(). (This can, again, be cleaned up afterward.)
Or, you can keep your CSS and your HTML separate, but also keep an internal documentation file (a "style guide") that describes how and when to use the CSS classes defined in the stylesheet. This is your in-context equivalent to the knowledge the LLM already has burned-in from training on the Tailwind docs site. Then, in your coding agent's instructions, you can tell it that when writing HTML, it should refer to the "style guide", rather than trying to reverse-engineer the usage of the styles from their implementation in CSS.
Re: Google AI Studio is now sponsoring Tailwind CSS
#87Re: Google AI Studio is now sponsoring Tailwind CSS
#88Will this change the situation of the 75% of engineers who just got laid off, or is this just to fund the framework, rather than the Tailwind Plus team?
If they have 3 left, that's 9 engineers. I doubt it'll bring them back unless this is a huge package. a few million only delays the inevitable by a year or 2.
Re: Google AI Studio is now sponsoring Tailwind CSS
#89Earlier quoted context omitted.
It seems to be in Google's interest to keep Tailwind CSS afloat. Tailwind CSS is alive -> New / existing projects keep using Tailwind CSS -> more code for Gemini to train upon -> better and fancier UIs being created through Gemini -> popularity and usage of Gemini doesn't go down Of course this applies to any other LLM provider too but I guess Google saw this opportunity first.
I think it'd be better for AI and web dev if AIs generated real CSS instead. The supposed difficulty of tracking from elements to classes to rulesets is something that AIs can easily handle, and being able to change a ruleset once and have the update apply to all use sites is really good for AI-driven changes. Plus, humans and AIs won't have to wait for Tailwind to adopt new CSS features as they are added. If the AI…
Re: Google AI Studio is now sponsoring Tailwind CSS
#90Ultimately it was Radix/Shadcn (which uses tailwind for styling of course) that killed the need to buy Tailwind’s UI kits by offering all these primitives with good default styling for free.
Also, the tailwind UI stuff feels pretty dated at this point in comparison to what’s offered in other free UI libraries these days.