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.
This "key piece of foundational web tech" was released 5 years ago and gained prominence maybe 2-3 years ago. Let's not exaggerate its impact. We were perfectly fine before Tailwind and will be fine after it.
Creators of Tailwind laid off 75% of their engineering team
681–690 of 893 posts
Re: Creators of Tailwind laid off 75% of their engineering team
#682Very sad to hear, I bought Tailwind UI years ago and although it was a lot more expensive than I wanted, I've appreciated the care and precision and highly recommend buying it (It's now called Tailwind Plus) even still (maybe even especially now). Mad props to Adam for his honesty and transparency. Adam if you're reading, just know that the voices criticizing you are not the only voices out there. Thanks for all you'…
> Btw the Tailwind newsletter/email that goes out is genuinely useful as well, so I recommend signing up for that if you use Tailwind CSS at all. What is the signup link? I googled a bit but couldn't find it.
Re: Creators of Tailwind laid off 75% of their engineering team
#683> But the reality is that 75% of the people on our engineering team lost their jobs here yesterday because of the brutal impact AI has had on our business. Adam is simply trying to navigate this new reality, and he's being honest, so there's no need to criticize him.
Some of the critics in the thread are… odious. I’ve written down some of the GH handles, because if I’m ever hiring again, I wanna make sure I’d never hire some of these folks. I don’t understand how someone can display such contempt towards the maintainer of a thing they’ve used for free.
Re: Creators of Tailwind laid off 75% of their engineering team
#684Earlier quoted context omitted.
If that's your goal, you probably shouldn't call the class bg-blue? It should be bg-blue-but-purple-on-mobile. But then it's definitely so specific it's the wrong way to select a style. If you want the page background to be blue but purple on mobile, write that in your CSS with a selector of "body" instead of ".bg-blue-but-purple-on-mobile"
The point being you can't do this with inline styles: "bg-purple md:bg-blue"
Re: Creators of Tailwind laid off 75% of their engineering team
#685Earlier quoted context omitted.
Thank you, that’s indeed much cleverer. Unfortunately I’ve closed my account this year, trying to put my money where my mouth is and not furthering the goals of GitHub or Microsoft.
What's wrong with microsoft and github? I can't lie, between this comment and the "writing down people's github handles out of spite just in case" you are coming off as someone with a lot of grievances.
Pull up a chair. This is going to take while...
Re: Creators of Tailwind laid off 75% of their engineering team
#686Earlier quoted context omitted.
> I usually find AI written CSS to be slightly visually flawed and almost always logically flawed. Funny, this also qualifies most of the _human_ written CSS I've seen. !important all the things!
It is funny how things that are hard for humans are also hard for LLMs
Re: Creators of Tailwind laid off 75% of their engineering team
#687Earlier quoted context omitted.
I could never afford Tailwind UI but then again I don’t really use Tailwind. That said, as an open-source styling solution, they could be supported in other ways. A lot — and I really mean a lot — of websites are built with Tailwind, yet very few consider donating or buying what they have to offer. Plenty of F/LOSS is in the same state: businesses extract all value they can from open-source, but put back nothing. Tha…
My current take is that if you start an open-source project now, you should go full AGPL (or similar copyleft license), and require a CLA for contributors. If your thing ends up actually good you now have a defence against exploitation, and a way to generate income reliably (by selling the code under a different license). afaik, organisations like the FSF even endorse this.
There are situations that the AGPL does not cover that could be considered leeching from the commons.
I think we need stronger licensing, and binding contracts that forfeit code recipients' right to fair use in order to hinder LLM laundering, along with development platforms that leverage both to limit exploitation of the commons.
Re: Creators of Tailwind laid off 75% of their engineering team
#688Earlier quoted context omitted.
I'm not going to dogpile criticism on Tailwind or Adam, whose behavior seems quite admirable, but I fundamentally agree with the thrust of the parent comment. It's unfortunate for Tailwind and anyone who was invested in the project's pre-2022 trajectory, but no one is entitled to commercial engagement by unaffiliated third parties. Here's a similar example from my own experience: * Last week, I used AI to help me pre…
Laws are not intellectual property of individuals or companies, they belong to the public. That's a fundamentally different type of content to "learn" from. I totally agree that AI can save a lot of time, but I don't agree that the creators of Tailwind don't see any form of compensation. It does not feel not right to me that revenue is being taken from Tailwind and redirected to Google, OpenAI, Meta and Anthropic wit…
While I am all for working out some sort of compensation scheme for the providers of model training data (even if indirect via techniques like distillation), that's a separate issue from whether or not AI's disruption of demand for certain products and services is per se harmful.
Re: Creators of Tailwind laid off 75% of their engineering team
#689Earlier quoted context omitted.
Some of the critics in the thread are… odious. I’ve written down some of the GH handles, because if I’m ever hiring again, I wanna make sure I’d never hire some of these folks. I don’t understand how someone can display such contempt towards the maintainer of a thing they’ve used for free.
I am one of those critics, but I never used Tailwind. A layoff of that magnitude is horrific, but if what they are describing as their business model is true, they really really need to rethink it. I wonder what the size of their marketing team is like, and if they were involved in the layoffs. Seems like they need some help there. I found the "downvote" spam in that thread, for reasonable posts, to be quite off-putt…
Left are the three owners of tailwind, one engineer and one ops+customer service + partner sails person.
Re: Creators of Tailwind laid off 75% of their engineering team
#690Earlier quoted context omitted.
Some of the critics in the thread are… odious. I’ve written down some of the GH handles, because if I’m ever hiring again, I wanna make sure I’d never hire some of these folks. I don’t understand how someone can display such contempt towards the maintainer of a thing they’ve used for free.
I am one of those critics, but I never used Tailwind. A layoff of that magnitude is horrific, but if what they are describing as their business model is true, they really really need to rethink it. I wonder what the size of their marketing team is like, and if they were involved in the layoffs. Seems like they need some help there. I found the "downvote" spam in that thread, for reasonable posts, to be quite off-putt…