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

Please Do Not Vibe Fuck Up This Software

github.com

Post reply on HN
Print view View original

91–100 of 534 posts

Re: Please Do Not Vibe Fuck Up This Software

#91

Post by croes »

Could be generalized to Please Do Not Vibe Fuck Up This Software.

Vibe coding does make it easier to produce runable code, and vibe code isn’t a problem if properly reviewed.

Seems like AI just exposed that it doesn’t happened properly.

Re: Please Do Not Vibe Fuck Up This Software

#92

Post by llbbdd »

Crazy to watch the death of open source happen in real time like this. Why would anyone share any code to open themselves up for all of these wannabe main characters to pile on them? Given the choice I'd rather have a bunch of slop coded PR contributions to wade through than whatever this entitled nightmare raider thread is.

Re: Please Do Not Vibe Fuck Up This Software

#94

Post by m132 »

Wow.

Rsync has to be one of the worst spaghetti projects I've worked with. It's an incredibly decent tool built around a well-though out algorithm, but its code is an exact opposite of what you'd expect. And it's written in C.

I'm not surprised letting Claude loose on it for roughly 2 months already caused visible breakage. The question is, with it being very obviously a bad idea, can the maintainer still be trusted if he let something like this happen?

Re: Please Do Not Vibe Fuck Up This Software

#95

Post by mort96 »

JodieBenitez wrote: post #85
theonemind wrote: post #14

I find the way that issue was opened incredible obnoxious, but it is baffling that the maintainers seem to have let AI loose on rsync. Like, why? Why try comparatively experimental crap when your fortune and reputation is made and you're the leader of a niche and immune to market pressure and the people love the thing and it does exactly what it's supposed to and works well? It's like the Matrix, with the little rant…

> the maintainers seem to have let AI loose on rsync is it an assumption ?

No: https://github.com/RsyncProject/rsync/commits/master/

Re: Please Do Not Vibe Fuck Up This Software

#97

Post by nelsonfigueroa »

relistan wrote: post #46

Hacker News: “It’s unfair the burden put on maintainers of the core pillars of open source software. Show some respect for the maintainers, and do your best to contribute.” … little changes … Also Hacker News: “I have the right to tell you how to manage the project that you created and have maintained for 30+ years, because I feel very self-righteous about AI and code quality!”

Goomba fallacy https://en.wiktionary.org/wiki/Goomba_fallacy

Re: Please Do Not Vibe Fuck Up This Software

#98

Post by michaelmrose »

nottorp wrote: post #42
roenxi wrote: post #16

Earlier quoted context omitted.

Are you basing this opinion on the issue or actual evidence? Because this github link, although interesting, is almost completely context free on what the drama is beyond "Claude". The rsync maintainers could be anywhere on the spectrum from the perfect and responsible maintainer to incompetent children and we couldn't really tell.

> is almost completely context free on what the drama is beyond "Claude" As soon as it happened their rsync based backup system that was working before started to fail. It says right there.

The source code is all right there. An actual analysis would involve a complete description of what you were doing including code they are running proving that what you were doing is reasonable and correct and expected to work. An explanation of what actually happened and ideally the exact commit where it stopped working.

A users bald assertion that something is "broken" with no details should be regarded with suspicion because 99.9% of the time the user is the cause of their own problems.

NOTHING is right there. Nothing whatsoever. No commits no use code no error messages no description. Nothing but dripping contempt for their betters.

Post reply on HN