Creators of Tailwind laid off 75% of their engineering team • Hacker News Board

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

#621

Post by mikeg8 » Thu, Jan 08, 2026, 1:57 AM UTC

mattgreenrocks wrote: post #231

Something’s wrong when a key piece of foundational web tech is staring down unsustainability. Tailwind is almost ubiquitous these days. It needs to continue to exist. Small businesses being eaten by AI is a net negative, because they’re in a unique position whereby they need to actually have to listen to customers vs just optimizing for a rando middle manger’s promotion in BigTech.

“Foundational” seems a bit overkill here. There is nothing foundational about it – it’s a convenience tool, albeit a very good one.

AI is disruptive technology - like other tech innovations before it, there will be casualties to incumbents. If anything, this just shows how small businesses with need to be more creative when establishing moats and sustainability in this new landscape.

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

#622

Post by kelnos » Thu, Jan 08, 2026, 2:01 AM UTC

satvikpendem wrote: post #302

khy wrote: post #89

Earlier quoted context omitted.

Tailwind Plus is great - I love the lifetime access, but I always wondered how sustainable that model was. Even without AI, how many of those memberships could they sell?

I thought the same, and yet on the other hand, how could they have done it differently? People don't want to pay a subscription just to write a DSL of CSS. Perhaps they could've done it per project like some companies, but I don't think it'd be as popular as their lifetime model. Ironic.

We can go back to how software was sold decades ago: you pay for version 1.0, and get bugfixes for the 1.x series. Then 2.0 is released, and if you want it, you pay again for the 2.x series. And so on.

I agree on not wanting a subscription for something like this. But I also acknowledge that if people are still doing work on something post-sale (beyond bugfixes for a pre-defined support period), I should maybe expect to have to pay for that continuing work.

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

#623

Post by twolf910616 » Thu, Jan 08, 2026, 2:02 AM UTC

The web is too open. Sad day to read these comments.

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

#624

Post by lone-cloud » Thu, Jan 08, 2026, 2:02 AM UTC

rhymnz wrote: post #608

lone-cloud wrote: post #585

Earlier quoted context omitted.

shadcn ui is not a component library but the basis for a component library that has great accessibility built-in from the start, so yes, it is a refutation.

You're thinking of Radix primitives which Shadcn is built on, but both are component libraries.

Maybe we're arguing semantics, but I think calling shadcn a "basis for a design system" is more accurate than a traditional component library. The difference to me is that shadcn lives inside your codebase and you can fully customize it as you please. You cannot customize a component library like MUI nearly to that extent.

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

#625

Post by cute_boi » Thu, Jan 08, 2026, 2:03 AM UTC

I feel very sad. The way AI is delivering, I suspect 90% will laid off within 2-3 years. I don't know myself what should I do in future.

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

#626

Post by re-thc » Thu, Jan 08, 2026, 2:05 AM UTC

c-hendricks wrote: post #373

re-thc wrote: post #333

Earlier quoted context omitted.

MUI sells paid components paid monthly. Definitely doable for the paid product.

I'm not super familiar with tailwind plus, but I am familiar with MUI. MUIs paid offerings are open-core, you pay for support and a couple of extra features. Tailwind plus looks like paying for basic components (checkboxes, sidebars, buttons) and it doesn't even offer anything like DataGrid (free with mui).

> and it doesn't even offer anything like

Shows Tailwind was just too little too late.

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

#627

Post by freedomben » Thu, Jan 08, 2026, 2:09 AM UTC

ZeroConcerns wrote: post #211

freedomben wrote: post #71

Earlier quoted context omitted.

Only if you ignore this part of my comment: > 95% of the value I get is the components and things If you want (and only want) a pre-built site that just needs populated with content and maybe minor tweaks to things, then yeah it's React world. However I've rarely found that any template site (Tailwind or otherwise) is close enough to where it doesn't need medium to major surgery to meet my needs, at which point it's…

> If you want (and only want) a pre-built site No, I want to be able to @import "tailwindcss" without feeling guilty. > I've rarely found that any template site Well, meet https://basecoatui.com -- and there's more where that came from. So, ehhm, no, I'm not ignoring the salient part of your comment: you are ignoring the entire point of my post, which is that if Tailwind had a non-React monetization strategy, things…

> No, I want to be able to @import "tailwindcss" without feeling guilty.

tailwindcss is and always has been free, so I don't understand why there would be any guilt with using it. Tailwind UI/Tailwind Plus is essentially pre-built components built using tailwindcss, plus some pre-built site templates.

> Well, meet https://basecoatui.com -- and there's more where that came from.

Thanks, that looks great and will be useful to me! However, unless I'm missing something basecoatui is a component library much like what Tailwind UI/Tailwind Plus provides (though organized differently and useful in a different way IMHO). The template sites are essentially complete websites that you just git clone and it's ready to run. Quite different. basecoatui would be very useful to me, whereas template sites rarely ever have been.

> So, ehhm, no, I'm not ignoring the salient part of your comment: you are ignoring the entire point of my post, which is that if Tailwind had a non-React monetization strategy, things maybe, possibly, might have worked out better.

Apologies if that came off harsh, I didn't mean to ascribe any malice to your reply. However, it seems like there's some confusion here about what the Tailwind "templates" are. They aren't a component library, the component library is different and is not React only.

So to summarize, there are two major parts that are different:

1. Templates (pre-built sites that you git clone). React only

2. Pre-built pieces/components that you copy/paste and modify into your existing app.

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

#628

Post by runako » Thu, Jan 08, 2026, 2:15 AM UTC

Sincerely hope the Tailwind team can navigate this rough patch.

Frontend output from LLMs is (in my experience) subpar when compared to human-built components. However, I am not primarily a frontend dev. I would definitely pay for something that let me easily build frontends using vetted components, in ways they were designed to work together.

This seems like something that would sit solidly in the bailiwick of framework designers like Tailwind Labs. But it seems they primarily target frontend developers, so their focus is elsewhere.

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

#629

Post by sreekanth850 » Thu, Jan 08, 2026, 2:17 AM UTC

blibble wrote: post #487

sreekanth850 wrote: post #115

Very sad. Any OSS project that depend fully on consulting will be on high risk. Platforms like deepwiki shrinks the knowledge gap massively.

there's no knowledge on deepwiki only slop

That is old thinking. Deepwiki is so much helpful. I use ABP framework and never had to ask the developer anything.

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

#630

Post by presentation » Thu, Jan 08, 2026, 2:21 AM UTC

biztos wrote: post #387

sosodev wrote: 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…

Is AI making component libraries redundant? Or is it just making it really easy to use free component libraries? (Or is it really more about traffic to the documentation site and thus eyeballs on the sales pitch?) I'm making an app using ShadCN, which is pretty good and free -- maybe Tailwind Plus would be significantly better, I don't know, I had to consider the possibility that this project never makes any money so…

Fwiw I don’t even think shadcn is good, but our app is built on top of those components already, so we can’t change it without changing everything, so we’re stuck with it.