101–110 of 893 posts
Earlier quoted context omitted.
It already exists. Tailwind has had GitHub sponsorships enabled for years but only 5 people have ever given them money that way.
They have off-GH sponsorship that's much more widely subscribed. https://tailwindcss.com/sponsor
EDIT: Doing the math on the sponsor list, it's probably around $1M in ARR now.
Sadly, 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…
It's just too ironic and such a shame that LLMs have railroaded the business model of Tailwind when LLMs have made it so much more popular. Does anyone have any backseat driver ideas for how tailwind could make enough money to hire a team to work on the framework?
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).
> [...] 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. And every second I spend trying to do fun free things for the community like this is a second I'm not spending trying to turn the business around and make sure the people who are still here are getting their paychecks every month. [...]
> Traffic to our docs is down about 40% from early 2023 despite Tailwind being more popular than ever. The docs are the only way people find out about our commercial products, and without customers we can't afford to maintain the framework.
> 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.
Agreed. Also I could not imagine being in his shoes, it must be heartbreaking seeing all his work burn like this.
Whats the 2026 version of "you should learn to code"?
> 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.
Sucks that anytime you ask AI to generate a site for you Tailwind will have an impact on that.
Earlier 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.
Regarding the point about accessibility, there are a ton of little details that must be explicitly written into the HTML that aren't necessarily the default behavior. Some common features of CSS and JS can break accessibility too.
None of this code would obvious to an LLM, or even human devs, but it's still what's expected. Without precisely written and effectively read-only boilerplate your webpage is gonna be trash and the specifics are a moving target and hotly debated. This back and forth is a human problem, not a code problem. That's why it's "hard".