Google AI Studio is now sponsoring Tailwind CSS
151–160 of 319 posts
Re: Google AI Studio is now sponsoring Tailwind CSS
#152This 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…
If the description for each tier is correct then it seems like Google AI Studio is an Ambassador only ($2,500 per month). This tier includes your company logo on the homepage. The Partner tier ($5,000 per month) includes placing your logo at the top of the sponsor list and Google AI Studio is at the end of the sponsor list. Edit Looking at the tailwind.css repo[1] they are a Partner. Not sure why they are at the end…
As part of FAANG, they should be donating like 10x that amount at least.
Disclosure: I am relying on your word, and do not know if there are more tiers above partner or not.
Re: Google AI Studio is now sponsoring Tailwind CSS
#153Earlier quoted context omitted.
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
#154This 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.
Re: Google AI Studio is now sponsoring Tailwind CSS
#155Earlier 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
#156Earlier 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.
class="menu-item"
Styles-in-HTML (Tailwind):
class="m-4 mb-2 p-2 border border-radius-sm border gray-200 hover:border-gray-300 font-sm sm:font-xs [...]"
You can be completely insensitive to or unbothered by the difference, but that doesn't mean they're equivalent.
Re: Google AI Studio is now sponsoring Tailwind CSS
#157Earlier quoted context omitted.
If the description for each tier is correct then it seems like Google AI Studio is an Ambassador only ($2,500 per month). This tier includes your company logo on the homepage. The Partner tier ($5,000 per month) includes placing your logo at the top of the sponsor list and Google AI Studio is at the end of the sponsor list. Edit Looking at the tailwind.css repo[1] they are a Partner. Not sure why they are at the end…
...which is not even a developer's salary. Pathetic from a company that makes billions and has surpassed even Apple in terms of market cap (yes, I know market cap means very little, especially in a bubble, but still...) As part of FAANG, they should be donating like 10x that amount at least. Disclosure: I am relying on your word, and do not know if there are more tiers above partner or not.
Re: Google AI Studio is now sponsoring Tailwind CSS
#158Earlier quoted context omitted.
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.
companies are suddenly sponsoring tailwind just for marketing
Re: Google AI Studio is now sponsoring Tailwind CSS
#159Earlier 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.
100% agree. If an open source project needs money to run, then isn't that defeating the purpose of being open source? Open source is a gift economy. If the owner can monetise it on the side then that is just a bonus.
As Stallman said: Think free as in free speech, not free beer.
Re: Google AI Studio is now sponsoring Tailwind CSS
#160But you can't have it both ways, it can't be just a simple CSS library that doesn't need that much money, but also expect a decade of work+ on it. After all, this originally stems from the fact that a PR attempting to improve something didn't get merged in; a technically finished project would have the same problem, but that would be the rule rather than the exception.