Where's the 75% layoff number from ? This thread is about making docs llm friendly.
if you actually read the thread: https://github.com/tailwindlabs/tailwindcss.com/pull/2388#is...
Creators of Tailwind laid off 75% of their engineering team
171–180 of 893 posts
Re: Creators of Tailwind laid off 75% of their engineering team
#172Why would a CSS library turn into a company? How do they even make money while there are hundreds of alternatives?
Bootstrap is more than enough for 99.99% of the projects, and it is free.
Re: Creators of Tailwind laid off 75% of their engineering team
#173Where's the 75% layoff number from ? This thread is about making docs llm friendly.
Adam added a comment to that thread with the 75% number and more context.
Re: Creators of Tailwind laid off 75% of their engineering team
#174I feel like you don't need engineers anymore. Bad news for all of us, but its just a fact of life.
Re: Creators of Tailwind laid off 75% of their engineering team
#175Earlier quoted context omitted.
hm, families need to eat.
Then why is HTTP, CSS and HTML free ? It's creators need to eat too. Should they start charging for it ?
Which of those are evolving at the rate of frameworks?
BTW I'm of the opinion that frontend tooling developers should actually try to contribute things to HTML and CSS instead of building "component libraries" on top of them.
If the native controls were good and if the browsers allowed using "uniformly styled" versions of them then there would be no good reason for such libraries to exist.
Re: Creators of Tailwind laid off 75% of their engineering team
#176Where'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...
Re: Creators of Tailwind laid off 75% of their engineering team
#177Earlier quoted context omitted.
I didn't ask how to do a bait and switch to offer a good free product and later ask for more money or else I'm going to make it worse. But I guess nuance is hard to understand. Also it's always funny when someone tries to look up your past instead of giving convincing arguments.
Arguments for... somebody wanting to get paid for their work? What are you doing?
Normally you ask for payment upfront, not years after.
Re: Creators of Tailwind laid off 75% of their engineering team
#178Earlier quoted context omitted.
It is "progress" when tech bros displace traditional workers, but it is "heartbreaking" when a tech bro gets displaced by other tech bros. Whats the 2026 version of "you should learn to code" ?
You should learn to vote for UBI?
Agreed, it's one of the only ways forward I can think of while still maintaining markets in some part of the economy...that is, if you care about the human condition at all. Plenty of these tech leaders seem to want to replace humanity though, so this will be an uphill battle.
Re: Creators of Tailwind laid off 75% of their engineering team
#179Earlier quoted context omitted.
WTF? So your answer to "how should open source projects achieve financial sustainability" is "don't even try"?
When you start making your open source project worse for your users because you are not making enough out of it I'll choose to use something else. There's a point where it's too much and it just feels like a trojan horse when later you stop caring for your free users.
I think the part you're missing here is that the author here is under no requirement to accept changes to their project and everyone else is welcome to fork it if they disagree with choices made by the author.
The author did not in fact, make the project worse, all they did was not accept a change, and that is entirely different than making it worse.
Even those who stood to benefit from the change have not received a degraded experience in comparison to the current state of affairs, but the same experience as the current state of affairs, since no change occurred. It is truly within the author's rights to do this, in any case.
One should avoid a sense of entitlement to additional and ever-increasing quantities of free work when free work has already been done.
Re: Creators of Tailwind laid off 75% of their engineering team
#180> our revenue is down close to 80%.
Damn