Does vibe coding risk destroying the Open Source ecosystem? According to a pre-print paper by a number of high-profile researchers, this might indeed be the case based on observed patterns and some…
Interesting. I thought this will be another post about slop PRs and bug reports but no, it’s about open source project not being promoted by AI and missing on adoption and revenue opportunities.
So I think we definitely see (and will see more) ‘templatization’ of software development. Some ways of writing apps that are easy to understand for AI and are promoted by it will see wider and wider adoption. Not just tools and libraries but also folder structures, design patterns and so on. I’m not sure how bad this will be long term. Maybe it will just stabilize tooling? Do we really need new React state management library every 6 months?
Hard to tell how will this affect the development of proper tools (not vibe coded ones). Commercial tools struggling to get traction will definitely suffer but most of the libraries I use are hobby projects. I still see good tools with good documentation getting enough attention to grow, even fairly obscure ones. Then again, those tools often struggle with getting enough contributors… Are we going to see a split between vibe coded template apps for junior devs and proper tools for professionals? Will EU step in and found the core projects? I still see a way forward so I’m fairly optimistic but it’s really hard to predict what will happen in a couple of years.
I am building a commercial application in my free time and I can definitely see evidence of this templatization. There are things that are very common in C# developer’s implementations which I deliberately don’t want to do. The AI will do it with reckless abandon. I can tell it not to, but it sneaks back in.
OSS library funding has been a huge issue in general. I really think the companies that have trillion dollar market caps can fund the development of top libraries but they just don’t.
Interesting. I thought this will be another post about slop PRs and bug reports but no, it’s about open source project not being promoted by AI and missing on adoption and revenue opportunities.
So I think we definitely see (and will see more) ‘templatization’ of software development. Some ways of writing apps that are easy to understand for AI and are promoted by it will see wider and wider adoption. Not just tools and libraries but also folder structures, design patterns and so on. I’m not sure how bad this will be long term. Maybe it will just stabilize tooling? Do we really need new React state management library every 6 months?
Hard to tell how will this affect the development of proper tools (not vibe coded ones). Commercial tools struggling to get traction will definitely suffer but most of the libraries I use are hobby projects. I still see good tools with good documentation getting enough attention to grow, even fairly obscure ones. Then again, those tools often struggle with getting enough contributors… Are we going to see a split between vibe coded template apps for junior devs and proper tools for professionals? Will EU step in and found the core projects? I still see a way forward so I’m fairly optimistic but it’s really hard to predict what will happen in a couple of years.
I am building a commercial application in my free time and I can definitely see evidence of this templatization. There are things that are very common in C# developer’s implementations which I deliberately don’t want to do. The AI will do it with reckless abandon. I can tell it not to, but it sneaks back in.
OSS library funding has been a huge issue in general. I really think the companies that have trillion dollar market caps can fund the development of top libraries but they just don’t.