Live data from Hacker News

Google AI Studio is now sponsoring Tailwind CSS

twitter.com

171–180 of 319 posts

Re: Google AI Studio is now sponsoring Tailwind CSS

#171

Earlier quoted context omitted.

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.

No, because many components have internals that need to be styled consistently with parts of other components.

With plain CSS components can easily share styles and use them by adding the correct class name to elements.

With Tailwind you have to copy your list of super fine-grained classes to each component, and try to keep them in sync over time

Re: Google AI Studio is now sponsoring Tailwind CSS

#172
post #111

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.

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

Or like 10 senior engineers in mid sized companies in Europe.

I wish every engineer were paid FAANG money.

Re: Google AI Studio is now sponsoring Tailwind CSS

#173

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.

That's how bloat happens.

Re: Google AI Studio is now sponsoring Tailwind CSS

#174

Earlier quoted context omitted.

I don't think I'm worried about defunding a trillionaire.

First they came for the trillionaires, and I did not speak out, because good.

Well by the time they eat the trillionaire I'll be dead. So be it. I don't think some site hosting microblogs is gonna be the downfall of such wealth, though.

Re: Google AI Studio is now sponsoring Tailwind CSS

#175

Earlier quoted context omitted.

First they came for the trillionaires, and I did not speak out, because good.

Well by the time they eat the trillionaire I'll be dead. So be it. I don't think some site hosting microblogs is gonna be the downfall of such wealth, though.

One can hope!

Re: Google AI Studio is now sponsoring Tailwind CSS

#176

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.

Every app that uses tailwind builds a custom CSS bundle. Tailwind Labs does not host those; whoever is making the app has to figure out their own hosting. So I’m not seeing the significant infrastructure costs?

Even if Tailwind were a shared hosted system like the common bootstrap CDNs of old… CDNs are dirt cheap for a small text file, even if it were loaded billions of times a month.

Some back of the napkin math suggests that it would cost about $300 per billion downloads for the current bootstrap.min.css file (gzip compressed, naturally) at North American network prices on one CDN I’ve used before. Or just $150 per billion globally if you're willing to use fewer PoPs. With browser caching, even split per domain, a billion downloads covers a very large number of users for a very large number of page loads.

Re: Google AI Studio is now sponsoring Tailwind CSS

#177
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.

Tailwind is not a FAANG, they are glorified frontend CSS devs

Running one of the world’s leading UI libraries is far more impactful than anything 99% of FAANG engineers have or will ever work on.

Re: Google AI Studio is now sponsoring Tailwind CSS

#178

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…

I’ve had zero problems getting Claude to generate CSS.

I generally ask for the following, from scratch for each project:

- A theme file full of variables (if you squint this actually looks a bit like Tailwind)

- A file containing global styles, mostly semantic, rather than just piles of classes

- Specific, per component styles (I often use Svelte so this is easy as they live in the component files and are automatically scoped to the component)

IMO there’s even less need for Tailwind with AI than there was before.

When I see people talking about how good AI is with Tailwind it just feels like they’re lazily copying each other without even trying to avoid unnecessary complexity.

Re: Google AI Studio is now sponsoring Tailwind CSS

#179

Earlier 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 problem is training data. How many modern web sites use raw CSS?

Enough that in my experience Claude is great at it and there’s even less justification for Tailwind if you’re using AI.

Re: Google AI Studio is now sponsoring Tailwind CSS

#180
post #26
post #19

Earlier quoted context omitted.

> Google has poured untold millions into open source over the last couple of decades, not just by sponsorships, but also by employing contributors, etc. And Google has profited untold hundreds of billions of open source over the last couple of decades. They just need to be reminded of it. Edit: Haha, getting downvoted! Never underestimate the power of tens of thousands of Googlers on HN... Look, I use Gmail, Google m…

Google is actually kind of infamous for not using much in the way of OSS software. The list of things I can think of is: * Linux * LLVM * Webkit/Chrome (which they have done the majority of contributions to for a long time) * Java & a little bit of Python

[deleted]
Post reply on HN