Earlier quoted context omitted.
I notice that you didn't answer their question: How should OSS be funded?
Ethically
Creators of Tailwind laid off 75% of their engineering team
151–160 of 893 posts
Re: Creators of Tailwind laid off 75% of their engineering team
#152I’ll be honest. I’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 t…
Re: Creators of Tailwind laid off 75% of their engineering team
#153Re: Creators of Tailwind laid off 75% of their engineering team
#154Can someone explain to me the advantage of writing class="bg-blue" instead of style="background-color: blue;" and why anyone ever thought they could make meaningful money from enabling the former?
Re: Creators of Tailwind laid off 75% of their engineering team
#155Earlier quoted context omitted.
Having worked on a design system previously I think most people, especially non-frontend developers, discount how hard something like that is to build. LLMs will build stuff that looks plausible but falls short in a bunch of ways (particularly accessibility). This is for the same reason that people generate div-soup, it looks correct on the surface. EDIT: I suppose what I'm saying is that "The paid products Adam ment…
I think you're overestimating how much people care about quality.
They almost completely just give money back if it fails/sucks, and they are still coming out ahead.
Re: Creators of Tailwind laid off 75% of their engineering team
#156Earlier quoted context omitted.
Ethically
What's the ethically bad thing Tailwind did here? Not merging that pull request?
I got bit by that many times and do my best to avoid it but when it happens it's a stab in the back.
Re: Creators of Tailwind laid off 75% of their engineering team
#157The 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…
Re: Creators of Tailwind laid off 75% of their engineering team
#158I can't get over the Author of the CR addi g his responses on TikTok.. What have we come to?
e.g. Tech changes all the time, that isn't an excuse to be a dick. e.g. ok dude, don't expect any future free work from me in the future on any of your projects going forward. Rude AF.)
also, I just realised, that PR is an excuse to get the library he made (https://github.com/quantizor/markdown-to-jsx) used within TailwindCSS :p
Re: Creators of Tailwind laid off 75% of their engineering team
#159Sadly, selling pre-made components and templates was never a sound business model, especially in the wake of AI. One thing I learned being on HN for so long and launching my own products is that a product is not a business . Don't conflate the two, at your peril. Lots of people make great products but actually turning that into a business is fundamentally a different skill. It seems like Tailwind grew too fast, havin…
Seems like it was an insanely profitable product, but a risky business.
Re: Creators of Tailwind laid off 75% of their engineering team
#160Companies like Vercel, Lovable, and Stackblitz should pay salaries to each of these engineers. Their business succeeded only because Tailwind exists.