Hackaday

Research suggests LLM-assisted 'vibe coding' may harm open source ecosystems by reducing direct interaction with projects, decreasing website visits and documentation usage, and eliminating organic library selection. The practice replaces developer engagement with chatbot interactions, potentially starving projects of community participation, bug reports, and revenue from sponsorships. Studies show AI coding assistants introduce 41% more bugs and reduce experienced developer productivity by 19%, while degrading cognitive skills. The statistical nature of LLMs means only the most prevalent dependencies in training data get used, similar to how 80% of Spotify artists receive minimal plays and compensation.

How Vibe Coding Is Killing Open Source

On the plus side, I developed my first fully functioning application.

AI will kill alot just like facebook did… 🧐 - We need to evolve through it!

Vibe coders without the discipline to personally understand, debug, or even look at the AI-generated code will be the ones that will bring the most damage.

The bug introduction Statistic needs to be balanced against the amount of code generated. We need stats on bugs per SLOC generated, not numbers of bugs per se. AI may generate 41% more bugs, and if it generated 41% more code, that would be break even, right? But if it generates 1000% more code then 41% increase in bugs is not too bad.

I’m in the middle of writing a blog post about this. I don’t think AI will kill open source. Instead, I think it will kill a lot of less complex plugins and apps that are licensed with GPL.
Linux will be safe because of its complexity BUT things like WP plugins are fucked. In fact, I’d say the WP plugin ecosystem is under threat… and without the plugin and theme ecosystem WP becomes a clunky antique CMS.
AI removed the main point of friction that allowed that ecosystem to thrive.
Open source apps licensed under permissive licenses like MIT or BSD will be safe but the supporting organizations will need to adapt their business models.