Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vibe coding kills open source

arxiv.org

Post reply on HN
Print view View original

11–20 of 304 posts

Re: Vibe coding kills open source

#11

Post by Cthulhu_ »

tomaytotomato wrote: post #6

I have been trying to use Claude code to help improve my opensource Java NLP location library. However trying to get it to do anything other than optimise code or fix small issues it struggles. It struggles with high level abstract issues. For example I currently have an issue with ambiguity collisions e.g. Input: "California" Output: "California, Missouri" California is a state but also city in Missouri - https://gi…

> I started the project in my brain and it has many flaws and nuances which I think LLMs are struggling to respect.

The project, or your brain? I think this is what a lot of LLM coders run into - they have a lot of intrinsic knowledge that is difficult or takes a lot of time and effort to put into words and describe. Vibes, if you will, like "I can't explain it but this code looks wrong"

Re: Vibe coding kills open source

#12

Post by positron26 »

avaer wrote: post #7
tosh wrote: post #4

generative ai increases ambition, lowers barriers more open source, better open source perhaps also more forking (not only absolute but also relative) contribution dynamics are also changing I'm fairly optimistic that generative ai is good for open source and the commons what I'm also seeing is open source projects that had not so great ergonomics or user interfaces in general are now getting better thanks to generat…

What do you think of the paper's research claims that the returns for maintainers are reduced and sharing is decreasing?

Without real finance model innovation, what returns?

Re: Vibe coding kills open source

#13

Post by forgotpwd16 »

avaer wrote: post #9
antirez wrote: post #8

I believe we will see a new huge wave of useful open source software. However don't expect the development model to stay the same. I was finally able to resurrect a few projects of mine, and many more will come. One incredible thing was the ability to easily merge what was worth merging from forks, for instance. The new OSS will be driven not much by the amount of code you can produce, but from the idea of software y…

We need a new git. (could be built on the current git) > One incredible thing was the ability to easily merge what was worth merging from forks, for instance I agree, this is amazing, and really reduces the wasted effort. But it only works if you know what exists and where.

Jujutsu?

Re: Vibe coding kills open source

#14

Post by wolfi1 »

lukan wrote: post #5

"Vibe coding raises productivity by lowering the cost of using and building on existing code, but it also weakens the user engagement through which many maintainers earn returns." I think the title is clickbait. The conclusion is: "Vibe coding represents a fundamental shift in how software is produced and consumed. The productivity gains are real and large. But so is the threat to the open source ecosystem that under…

do you have experience in reviving an abandoned project? which way did you go? what would be a sensible approach?

Re: Vibe coding kills open source

#15

Post by earino »

lukan wrote: post #5

"Vibe coding raises productivity by lowering the cost of using and building on existing code, but it also weakens the user engagement through which many maintainers earn returns." I think the title is clickbait. The conclusion is: "Vibe coding represents a fundamental shift in how software is produced and consumed. The productivity gains are real and large. But so is the threat to the open source ecosystem that under…

Two of the authors are engaging on bluesky regarding the "clickbaityness" of the paper:

https://bsky.app/profile/gaborbekes.bsky.social/post/3md4rga...

(Note, I receive a thanks in the paper.)

Re: Vibe coding kills open source

#16

Post by mg74 »

avaer wrote: post #9
antirez wrote: post #8

I believe we will see a new huge wave of useful open source software. However don't expect the development model to stay the same. I was finally able to resurrect a few projects of mine, and many more will come. One incredible thing was the ability to easily merge what was worth merging from forks, for instance. The new OSS will be driven not much by the amount of code you can produce, but from the idea of software y…

We need a new git. (could be built on the current git) > One incredible thing was the ability to easily merge what was worth merging from forks, for instance I agree, this is amazing, and really reduces the wasted effort. But it only works if you know what exists and where.

More we need a new GitHub.

Re: Vibe coding kills open source

#17

Post by positron26 »

lukan wrote: post #5

"Vibe coding raises productivity by lowering the cost of using and building on existing code, but it also weakens the user engagement through which many maintainers earn returns." I think the title is clickbait. The conclusion is: "Vibe coding represents a fundamental shift in how software is produced and consumed. The productivity gains are real and large. But so is the threat to the open source ecosystem that under…

What even is "engagement" here? Seems like abstract harm that rationalizes whatever emotion the reader already feels.

Re: Vibe coding kills open source

#19

Post by cess11 »

ktallett wrote: post #2

I think vibe coding would greatly struggle with large open source projects unless your planning was exceptional and your comments on optimal coding style was exceptional, however...... For those small open source tools that many of us use daily and find invaluable, I actually think vibe coding is ideal for that. It can make a functional version quickly and you can iterate and improve it, and feel no loss for making i…

The authors try to study the effect of people not engaging directly with OSS projects because they substitute for this with a gang of chatbots, and draw the conclusion that this lack of contact with actual people means they'll be less likely to help finance OSS development.

Re: Vibe coding kills open source

#20

Post by data-ottawa »

ktallett wrote: post #2

I think vibe coding would greatly struggle with large open source projects unless your planning was exceptional and your comments on optimal coding style was exceptional, however...... For those small open source tools that many of us use daily and find invaluable, I actually think vibe coding is ideal for that. It can make a functional version quickly and you can iterate and improve it, and feel no loss for making i…

There are three or four projects I've always wanted to do, but were frontloaded with a lot of complexity and drudgery.

Maybe the best feature of vibe coding is that it makes the regret factor of poor early choices much lower. Its kind of magic to go "you know what, I was wrong, let's try this approach instead" and not having to spend huge amounts of time fixing things or rewriting 80% of the project.

It's made it a lot more fun to try building big projects on my own, where I would go into decision paralysis or prematurely optimize and never start the meat or learning of the core project.

Its also been nice to have agents review my projects for major issues, so I feel more confident sharing them.

Post reply on HN