I think it's happening, some of them are even making it to the front page of HN, like the "I built 50 calculators" a few days ago. I'm still working to release some of the things I've built over the last month:

- A nice little single-file web "random slideshow" to replace an aging one I bought. - A fairly feature-complete read-only SQL console. - A development SMTP server (like Mailhog) https://github.com/linsomniac/smtphotel - A work status dashboard that I'll probably release once I have run it a bit longer. - A fairly extensive Docusign-like webapp. - A retrospective meeting runner. - A cron "swiss army knife" helper. - A "social calorie tracker" (I'm unhappy with the existing ones out there).

These are all things I've vibecoded in the last month, and are more than I could have coded in my spare time in 6 months or more.

For me, the renaissance is here.

The incentive for sending in patches was that you needed to fix a bug in software you were using for your own use case, so you might as well send the authors the patch, and they'd keep maintaining it all for you. But if you can vibe-code your own solution, you don't need to use somebody else's software, so the patch doesn't get made, much less submitted.

The other thing is, LLMs tend to generate terrible code that pisses off open-source maintainers. So I'm not sure even LLM-made patches will make it into open source much.

This might be the death of traditional open source. Vibe-coded-only open source may be the next generation. Which I'm fine with, as long as we can start regulating software, so that vibe-coded tools are banned for safety/privacy uses unless they follow a software building code.