Ai, Tailwind And Traffic

Tailwind laid off 75% of its engineering team. Not because the product failed. Not because growth slowed. Tailwind is more popular than ever.

Usage is up. Revenue is down nearly 80%. That contradiction is the lesson. AI is not killing open source. AI is killing how open source makes money.

Tailwind monetized through documentation. Read the docs. Discover the ecosystem. Buy the paid products. That funnel worked when humans explored. It breaks when machines answer.

Vibecoding changed behavior. Developers do not read docs anymore. They ask an LLM, paste the output, and move on. No docs visit means no discovery. No discovery means no conversion. No conversion means layoffs. The software still wins. The company loses.

Popularity no longer equals sustainability. That assumption is dead. AI recommends stable, well known libraries because they reduce bugs and cognitive load. That accelerates open source adoption while quietly erasing its monetization surface. The better your library is, the more AI abstracts it away.

Quality cannot be vibecoded. Not yet. But monetization still depends on human attention, and AI removes attention from everything it touches.

I think that reading the docs is very important in the age of vibecoding, to vibecode better but not very important if you are not building something serious.

The real risk is not AI. The real risk is losing full time maintainers. Quality does not emerge from prompts.

AI did not end open source. It exposed weak revenue assumptions. If you are building dev tools today, ask one question. How does this make money when the user never sees your website? If you cannot answer that, growth will not save you.

To be honest, as an open source maintainer i never pondered on the question!

Waiting to see how this unfolds.