The vibecoded apps all rely on an army of users exploring the program and reporting all the bugs and edge cases. You don’t want to be doing that on your own.
it seems like the open-source space is losing some aspects of collaboration. people used to search for already existing projects on some git-hosters, maybe fork them or put effort into the existing thing. now half a dozen people each run their own race using AI, each solution misses 30% of the features and has x-amounts of bugs.
work together ffs :( i mean, 20 people can use AI to vibecode the same project, why does everyone now feel the need to do everything solo. (because they want to be the prolific founder and cool dude who did the most in the project* instead of being one of many contributors, i assume...)
*or rather, their AI.
I'm not too sure what the future here looks like and if this is even a problem, but things certainly are changing. These days submitting a well written bug report or feature suggestion, or validating existing reports is more useful than sending a PR.
Right, and that's something I already argued for since the very beginning of GenAI, namely that suddenly being very costly, economically and ecologically, is not that bad if you build upon what exists and collaborate on progress.
... except that's exactly WHY vibecoded project exist : they do NOT have to give a shit with existing codebase and agree on weird rules. They just start from "scratch". In fact I'm convinced there is the Ikea effect at play, namely that the PM of the vibe coded project is emotionally attached, even proud, of the result they think they provided somehow, despite them not actually doing it. Obviously for-profit GenAI companies have a big incentive to maximize token use and will never promote workflows and tool that minimize the one thing they monetize.
So even though I agree in theory, in practice I think there is little to no overlap.