Just charge a bucks for every deployment or something. Most of will easily pay a dollar. Tailwind should not be free, its good.
I think you're underestimating the composition.
Creators of Tailwind laid off 75% of their engineering team
321–330 of 893 posts
Re: Creators of Tailwind laid off 75% of their engineering team
#322Earlier quoted context omitted.
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.
It's a nice fantasy but completely contrary to human nature.
Glad to hear you've isolated the UBI-incompatibility (UBII) gene. Could you present your findings for the rest of us?
Re: Creators of Tailwind laid off 75% of their engineering team
#323Earlier quoted context omitted.
If there's anything AI coding is good at, it's writing react components and tailwind css.
If you want a bunch of tailwind class slop, then yes. Otherwise, A lot of context engineering is needed if you want it to write modular tailwind components properly for large projects where consistency is important.
[deleted]
Re: Creators of Tailwind laid off 75% of their engineering team
#324Where's the 75% layoff number from ? This thread is about making docs llm friendly.
ctrl+F 75%
Re: Creators of Tailwind laid off 75% of their engineering team
#325Earlier quoted context omitted.
What's the ethically bad thing Tailwind did here? Not merging that pull request?
I'd feel lied to if someone offers me a free tool and later the person that controls it chooses to make it worse just to make more money. 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.
So which part did he make it worst?
By not adding an extra "feature" you deemed as essential?
Even more surprising is this is from an 2012 account.
Re: Creators of Tailwind laid off 75% of their engineering team
#326My surprise is that the tailwind creator could have a engineering team based in a css framework that basically was used for people that didn't knew real css. Is normal that this people now use other products more effective how AI for this task.
I know CSS and was quite sceptical about tailwind before I used it in anger.
I was going to write a longer response, but instead I keep reading your last sentence:
> Is normal that this people now use other products more effective how AI for this task.
I think it's too early to tell on that.
Re: Creators of Tailwind laid off 75% of their engineering team
#327Companies like Vercel, Lovable, and Stackblitz should pay salaries to each of these engineers. Their business succeeded only because Tailwind exists.
Welcome to the internet, most of it is build by unknown OSS developers, how many people will you go ask these companies to pay for?
Re: Creators of Tailwind laid off 75% of their engineering team
#328Earlier quoted context omitted.
I can't imagine how it could work internationally, when people can literally migrate between countries and countries ain't sharing resources for free
They can? How many times have you migrated? Try going from the Middle East or Africa to any developed country.
You are joking right? There were handred of thousands of people that did this in last ten years or so to EU.
Re: Creators of Tailwind laid off 75% of their engineering team
#329The biggest miss from Tailwind is ignoring the rest of the ecosystem. Rightly or wrongly, everyone has moved on to using shadcn's system for components. Tailwind hasn't. Tailwind has excellent components available through Plus which are worth paying for but they're not available where people are, which pushes people towards other libraries built on top of Tailwind. I have paid for Tailwind Plus and I like their Catal…
> everyone has moved on to using shadcn's system for components
This may be an exaggeration.
Re: Creators of Tailwind laid off 75% of their engineering team
#330Earlier quoted context omitted.
Every project I worked on that used CSS was a mess. It's always 1000 line SCSS files and nobody knows what is going on there.
> and nobody knows what is going on there. For what its worth, I had the same experience with Tailwind. I regularly see classes that don't have an meaningful outcome. I don't think the problem is Tailwind or CSS (well, I guess Tailwind is CSS with extra steps but you get the idea) syntax (or any of the CSS preprocessors), but the fact that styling in browsers has accumulated a lot of cruft, and people who haven't "gr…
> I regularly see classes that don't have an meaningful outcome.
You mean custom classes?