Live data from Hacker News

Creators of Tailwind laid off 75% of their engineering team

github.com

181–190 of 893 posts

Re: Creators of Tailwind laid off 75% of their engineering team

#181
It's insane how much AIs use Tailwind and yet the companies aren't contributing anything. It would be trivial for Anthropic or Cursor to pay something.

Would it work to have a new free-use license that explicitly excludes LLMs? Make them pay royalties - you'd have to use something like public license keys. But if Spotify pays a trivial license payment for every stream - Claude could contribute something when it recommends a project.

Re: Creators of Tailwind laid off 75% of their engineering team

#183
post #67

Earlier quoted context omitted.

I think you're overestimating how much people care about quality.

If you can produce something that works 80% of the time for 5% of the cost? People take that all the time when they buy cheap shit off Temu or Amazon. They almost completely just give money back if it fails/sucks, and they are still coming out ahead.

Amazon (AWS) is not cheap! :D

Re: Creators of Tailwind laid off 75% of their engineering team

#184
post #90

It's just too ironic and such a shame that LLMs have railroaded the business model of Tailwind when LLMs have made it so much more popular. Does anyone have any backseat driver ideas for how tailwind could make enough money to hire a team to work on the framework?

I was going to say before LLMs Tailwind UI helped me get moving much faster on front-end code. Now I wish there was some kind of context I can provide to use the Tailwind UI instead of hallucinating its own. Tailwind UI still looks better than the generic stuff LLMs generate. (Open to any suggestions to feed existing ui components from Tailwind into my projects/llm).

There might be a business model for Tailwind here. I was looking at buying Tailwind Plus after reading this news, and my first question was how to get AI to use it efficiently.

Re: Creators of Tailwind laid off 75% of their engineering team

#185
post #26

The paid products Adam mentions are the pre-made components and templates, right? It seems like the bigger issue isn't reduced traffic but just that AI largely eliminates the need for such things. While I understand that this has been difficult for him and his company... hasn't it been obvious that this would be a major issue for years? I do worry about what this means for the future of open source software. We've lo…

Well, you can tell from the tone of his post that he isn't blaming anyone directly. They monetized convenience, and something more convenient came along.

I think it's more shocking to everyone how quickly something like that happens.

Re: Creators of Tailwind laid off 75% of their engineering team

#187
post #26

The paid products Adam mentions are the pre-made components and templates, right? It seems like the bigger issue isn't reduced traffic but just that AI largely eliminates the need for such things. While I understand that this has been difficult for him and his company... hasn't it been obvious that this would be a major issue for years? I do worry about what this means for the future of open source software. We've lo…

> The paid products Adam mentions are the pre-made components and templates, right? It seems like the bigger issue isn't reduced traffic but just that AI largely eliminates the need for such things.

Or more cynically that it eliminates the need to pay for such things. Claude and friends were no doubt trained on the commercial Tailwind components, so the question becomes whether those models could have done the job of Tailwind UI without piggybacking on the unpaid labour of the Tailwind UI developers. If not then we clearly have a sustainability problem here - someone still has to do the hard work to push things forward, but with the knowledge that any attempt to profit from that work will be instantly undercut by the copyright laundering Borg.

Re: Creators of Tailwind laid off 75% of their engineering team

#188

Where's the 75% layoff number from ? This thread is about making docs llm friendly.

I listened to his podcast this morning where he mentions 75% of their four person engineering team was laid off (only the founders and one engineer remain) https://adams-morning-walk.transistor.fm/episodes/we-had-six...

75% is a lot more dramatic than 3 people geez

Re: Creators of Tailwind laid off 75% of their engineering team

#189

Can someone explain to me the advantage of writing class="bg-blue" instead of style="background-color: blue;" and why anyone ever thought they could make meaningful money from enabling the former?

The advantage is in both the speed of the shorthand when transferring the CSS you know you need for a layout from your brain to the element (flex items-center gap-2 vs. display: flex; align-items: center; gap: .5rem; - just try typing them both out), plus all the stuff inline styles can't do, such as variants based on screen size, colour scheme, user preference, pseudo-classes, parent/sibling state, etc. which you can get done in one place in one file in one sitting.

The money wasn't coming from that.

Re: Creators of Tailwind laid off 75% of their engineering team

#190

Sadly, selling pre-made components and templates was never a sound business model, especially in the wake of AI. One thing I learned being on HN for so long and launching my own products is that a product is not a business . Don't conflate the two, at your peril. Lots of people make great products but actually turning that into a business is fundamentally a different skill. It seems like Tailwind grew too fast, havin…

Tailwind had several times more than 2M / ARR at their peak.
Post reply on HN