> 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.
Creators of Tailwind laid off 75% of their engineering team
141–150 of 893 posts
Re: Creators of Tailwind laid off 75% of their engineering team
#142Earlier 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 ?
HTML and CSS are free to use but the W3C is funded by membership fees.
Re: Creators of Tailwind laid off 75% of their engineering team
#143Earlier 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.
Re: Creators of Tailwind laid off 75% of their engineering team
#144Companies like Vercel, Lovable, and Stackblitz should pay salaries to each of these engineers. Their business succeeded only because Tailwind exists.
Re: Creators of Tailwind laid off 75% of their engineering team
#145Earlier quoted context omitted.
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).
Does asking for tailwind directly in the prompt not get it looking in that direction? I wonder if you could get a large enough context to include the css directly too
Re: Creators of Tailwind laid off 75% of their engineering team
#146I’m a contributor to this.
I’ve been CSS since the mid 2000s and I have a lot of it memorized by heart.
My team uses tailwind, therefore I use tailwind
But I don’t want to reconfigure my mental model to think in esoteric shorthand, when I already have vanilla web tech memorized.
So I just write some code to match the design and then I let an llm transform it into what my team expects.
I’m sharing in the hopes that the tailwind team can figure out a middle ground because I think a service that can take any valid styled content and output the same result in tailwind would be a niche small language model that solves the use case for why I don’t go to the docs.
Re: Creators of Tailwind laid off 75% of their engineering team
#147[flagged]
Re: Creators of Tailwind laid off 75% of their engineering team
#148[flagged]
hm, families need to eat.
We are a deeply unserious society.
Anyway; good luck going viral online, everyone. I got lucky, have had generational wealth in my back pocket since birth, am off the hook for you by our social norms. Hopefully it works out for you because I and the rest of us won't be engaged in political action on your behalf. Dance for the organ!
Re: Creators of Tailwind laid off 75% of their engineering team
#149Re: Creators of Tailwind laid off 75% of their engineering team
#150Earlier quoted context omitted.
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 notice that you didn't answer their question: How should OSS be funded?