For every Tailwind, there will be 1000x other projects affected by AI's use of OSS that will not get sponsored.
yep, companies tweeting "We are now sponsoring tailwind" is just marketing, if they were honest they would be sponsoring all OSS they use
Google AI Studio is now sponsoring Tailwind CSS
141–150 of 319 posts
Re: Google AI Studio is now sponsoring Tailwind CSS
#142Trump with greenland, and then obsession with tailwindcss. World needs a shakeup :D.
Re: Google AI Studio is now sponsoring Tailwind CSS
#143I love tailwind, but I think it’s disingenuous for Adam to claim that “AI” killed the tailwind UI kit business. Ultimately 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 librari…
Agreed. Also if they had really been trying to drive ARR, they would have made Tailwind UI a subscription/yearly licensing thing instead of a one-time purchase. There's a reason companies like Adobe/Microsoft switched away from one-time purchase software, and that reason is that it is exhausting and eventually impossible to sustain a business where you have to hunt for brand new customers every single month just to k…
Paying a yearly subscription for UI templates/components/kits is beyond a crazy idea.
You can't compare it with software licensing subscriptions.
Re: Google AI Studio is now sponsoring Tailwind CSS
#144This should be standard industry practice. Any company above a certain size should contribute financially to all software it depends on.
Tell that to the FOSS zealots....
Re: Google AI Studio is now sponsoring Tailwind CSS
#145Vercel is also now sponsoring Tailwind CSS: https://x.com/rauchg/status/2009336725043335338
I was honestly surprised they weren't already, given how heavily they use and promote it! Good to see they are helping out now too, though.
Looks like Vercel has been sponsoring Tailwind's hosting for a while - but glad to see Vercel starting to officially sponsor Tailwind! https://x.com/adamwathan/status/2009298745398018468
Re: Google AI Studio is now sponsoring Tailwind CSS
#146Earlier quoted context omitted.
Can you explain? Tailwind massively reduces overhead for abstraction, classing, documentation, and maintenance.
AFAICT, Tailwind is largely (not entirely) a different, shorter syntax for writing inline styles. (E.g., "class: 'bg-white'" = "style: 'background-color: white'".) If you've rejected structural CSS to begin with, I sort of get the point that it saves a lot of typing; otherwise I don't see how it helps all that much over SASS or just modern plain CSS.
Tailwind is a dirty hack, normally you are supposed to declare a class, which you apply to items of the same concept. This is the cause for CSS to exist.
Front devs got lazy, and started writing for each element, position: absolute; left:3px, top:6px, color:red;...
You could write Hello this would be similar "cleanliness"
Re: Google AI Studio is now sponsoring Tailwind CSS
#147Earlier 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.
What kind of headcount do you estimate $1MM/year can reliably support? That's like ~2 engineers at FAANG.
FAANG isn't the world.
Salaries for developers are well under $150k in most of the United States, for example, and that is for senior engineers. Most startups are paying $90k-$140k for senior devs, for example (I haven't done the math, but from my own experience, $100-$120k is the general sweet spot). Larger companies pay a bit more, but move beyond that and you are talking management.
Re: Google AI Studio is now sponsoring Tailwind CSS
#148Earlier quoted context omitted.
Counter-argument: the cascade in CSS was a massive design mistake and it shows even more in this particular case. With LLM-assisted development you spend more time reading and reviewing the generated code. The cascade in styles is nowhere near as readily apparent as something like Tailwind.
I haven't seen cascades be a problem since the days of monolithic, app-wide stylesheets, and no project I personally know of works that way anymore. Just about everyone uses component-specific styles with a limited set of selectors where there are very few collisions per property, and pretty clear specificity winners when there are. If the alternative to the cascade is that you have to repeat granular style choices o…
> Just about everyone uses component-specific styles
Yeah.
At which point you can simply use e.g Tailwind.
Re: Google AI Studio is now sponsoring Tailwind CSS
#149Earlier quoted context omitted.
Lots of great engineers will work for way less than a FAANG salary as long as it means not having to work for FAANG. $1m/year still won't get you all that much though.
Realistically if you can work on a small and high profile project like tailwind you're gonna be snatched up by someone willing to pay you at or near FAANG levels
That's good. We can tell people that so they will submit us patches for free.
Maybe we could even have a neat website with a leaderboard of sorts where we honor top contributors like some kind of gamification.
I think we would really need about five highly opinionated people with good technical and people skills to volunteer as paid maintainers for tailwind or any oss project to succeed.
Re: Google AI Studio is now sponsoring Tailwind CSS
#150Earlier quoted context omitted.
Counter-argument: the cascade in CSS was a massive design mistake and it shows even more in this particular case. With LLM-assisted development you spend more time reading and reviewing the generated code. The cascade in styles is nowhere near as readily apparent as something like Tailwind.
If you're arguing down that route, LLMs can bulk-apply style attributes exactly where they're needed. Every element precisely described, no need for CSS and style-sheets at all.
And then you'd wind up with a needlessly noisy approach, and then you will reach for Tailwind to do basically the same thing but in a more terse manner. ;P