Creators of Tailwind laid off 75% of their engineering team

Re:Creators of Tailwind laid off 75% of their engineering team by satvikpendem on Wednesday January 07, 2026 @02:28PM (#46531256)

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.

[ Parent | on HN ]

Re:Creators of Tailwind laid off 75% of their engineering team by re-thc on Wednesday January 07, 2026 @02:47PM (#46531537)

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

[ Parent | on HN ]

Re:Creators of Tailwind laid off 75% of their engineering team by c-hendricks on Wednesday January 07, 2026 @03:13PM (#46531887)

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).

[ Parent | on HN ]

Re:Creators of Tailwind laid off 75% of their engineering team by re-thc on Wednesday January 07, 2026 @09:05PM (#46536220)

> and it doesn't even offer anything like

Shows Tailwind was just too little too late.

[ Parent | on HN ]

Re:Creators of Tailwind laid off 75% of their engineering team by kelnos on Wednesday January 07, 2026 @09:01PM (#46536180)

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.

[ Parent | on HN ]