Vibe coding is thriving. The tools powering it are quietly dying.

This is a really important tension people aren’t talking about enough.

Open source used to monetize through attention: docs traffic, consulting, ecosystem tools, community visibility. If AI becomes the interface layer, that attention disappears. The usage stays high, but the relationship with the project weakens.

The scary part isn’t Tailwind specifically. It’s smaller infra libraries maintained by one or two people. The ones that don’t have VC backing or a SaaS wrapper. Those are the most fragile.

I don’t think open source dies. But the funding model probably has to change. Maybe AI companies need to contribute more directly, because they’re extracting massive value.

Otherwise yeah, we’re building on foundations that no one is incentivized to maintain.

Not an immediate risk but many backend frameworks I fear are gonna be in danger.

The tailwind situation also highlights something important. Enterprise backing has more power over open source than ever. If no one will donate because of no traffic, then sponsors will gain the upper hand.

Look at how Anthropic owns bun now.

What happens when the large companies, the industry titans decide to finish the cycle.

Embrace, Extend, Extinguish.

We are speedrunning our way back to the mainframe era. where code is proprietary and open source projects go unmaintained.

I feel this deeply. I use AI tools every day and honestly, I rarely visit docs anymore. It saves me time but I never think about who maintains the tools behind the scenes. If those projects fade away, my workflow collapses. I'm benefiting now but I'm not sure I'm sustaining what I rely on.

This hits close to home. I'm building Aitinery (AI travel planner) on Next.js + Tailwind CSS 4, and I realized I almost never visit the Tailwind docs anymore — Cursor and Claude generate the utility classes directly. I'm literally part of the problem this thread describes.

The paradox is brutal: the better AI gets at generating framework-specific code, the less we interact with the original docs and paid features. AI created a bypass around the entire monetization funnel.

As for which open-source project is most at risk next — I'd say anything that monetizes through docs traffic, tutorials, or freemium UI components. If AI can just generate the components, why pay for the premium ones?

The uncomfortable truth is that we (builders) need to start actively supporting the open-source tools we depend on, not just consume them through AI proxies. I've started sponsoring a few projects on GitHub. It's a small thing, but if enough of us do it, it could help bridge the gap while the ecosystem figures out new sustainability models.

I’ve noticed this too — I use Tailwind daily now but visit their site way less than before. Makes me realize how much we rely on open source without giving back enough.

Honestly the irony isn't lost on me - I build AI tools as a side thing and vibe-code all of them, so I'm literally part of the problem you're describing.

The thing I think about more than the business model dying is training data. Models right now were trained on years of organic community activity - docs visits, issues, PRs, Stack Overflow. Break that loop and future models train on a frozen snapshot from whenever the collapse happened. Vibing code in 2028 might mean applying 2024 best practices.

I throw money at a few OSS projects mostly out of guilt at this point. Not a solution but it's something.

The money in oss has not only been in creating tools and libs that anyone can use for free - but providing a competitive service that can be monetised. The way we do oss will evolve to account for the use of LLMs.

Eg: I use Codex a lot to build stuff and a lot of my repo is os - I've built a video editing tool that anyone can use / copy. Of course it already uses the ffmpeg and yt-dlp libs - but even if I hadn't, I'd have had to write python scripts to do all the work and then open sourced that.

I think it's important for us to support the oss community, but I'm guessing we'll have to evolve too.

Can't an open source project use AI to build out it's corpus to solve new problems (which will at some point be folded into a model via training)? I think the mistake here is conflating the purpose of open source. It's not to have folks visit docs for traffic, revenue or community - it's to provide a 'free as in speech, not as in beer' alternative to closed source software.

This hits hard. AI is amazing for productivity, but the invisible cost on open-source maintainers is huge. I’ve started consciously contributing back to the projects I rely on — even small PRs or donations feel necessary now 🙏