Live data from Hacker News

Please Do Not Vibe Fuck Up This Software

github.com

151–160 of 534 posts

Re: Please Do Not Vibe Fuck Up This Software

#151

Earlier quoted context omitted.

No, that's usually to decrease the number of bugs and vulnerabilities.

That's not why people rewrite in Rust. Rewrites brings new bugs regardless of the language.

You're conflating why people want to rewrite it in Rust vs what is the likely end result i.e. I do think people want to rewrite things in Rust because they believe long-term it will mean fewer (memory safety etc.) bugs especially because there's been almost no meaningful improvement in this space for a long time. But of course in the short term it will mean regressions compared to the established C written version.

That is different from AI where the calculus seems to be that if AI isn't involved, it aien't relevant.

Re: Please Do Not Vibe Fuck Up This Software

#152

Genuinely wondering though: is the problem that the patch was vibe coded, or is that no one reviewed the changes?

"Vibe coding" implies the changes weren't reviewed. That's the most common definition of the term.

Even if the developer himself didn't say that, though, it's safe to assume no AI generated commit beyond a very small size is ever properly reviewed (in the sense that the entire code is actually understood) because doing so would take longer than actually writing the code by hand like a caveman.

Re: Please Do Not Vibe Fuck Up This Software

#153
post #36

I truly don't get it You have a rock solid piece of software used by an infinite amount of people and other services. It works fine, does it's job and just have some time to time updates due to minor bug fixes. Why do we need AI here? And more over, why people is saying "fork it and use the previous version". It should be actually all the way around, create a parallel fork younamethetool-ai and keep the OG untouched.…

Why would it be the maintainer’s responsibly to fork their own repo? It wouldn’t even make sense; who would maintain the old repo?

They also don’t need a reason, or owe you their reason, for changing what tools they use to work on their open source projects.

Re: Please Do Not Vibe Fuck Up This Software

#155
post #63

Earlier quoted context omitted.

[flagged]

> Then somebody screenshots the geographical location "Israel" to attack another commenter. He gets lots of upvotes for it, too. And you got downvoted for calling out that crap. A sad state this world is in.

Yep.

When someone does that, he gets rightfully called out.

On the other side, accusations of being Russian trol are pretty common, even here on HN.

Why are people more sensitive to antisemitism than to antislavism?

Double standards, or just a hate induced by decades / centuries of indoctrination?

Re: Please Do Not Vibe Fuck Up This Software

#156
post #36

I truly don't get it You have a rock solid piece of software used by an infinite amount of people and other services. It works fine, does it's job and just have some time to time updates due to minor bug fixes. Why do we need AI here? And more over, why people is saying "fork it and use the previous version". It should be actually all the way around, create a parallel fork younamethetool-ai and keep the OG untouched.…

> Why do we need AI here? AI psychosis is a real thing and an actual mental health issue.

funny speculative question: psychosis is evidently a gradient. Does AI just highlight latent general psychosis (i.e. in the simplified interpretation of a worldview shaped more by unchecked belief and fantasy than observation) in otherwise largely functional people?

What if the problem is that we train people too much to take things that are being said at face value without questioning/observing them, increasing the psychosis problem?

Re: Please Do Not Vibe Fuck Up This Software

#157

I also hate the ai slop but on the flip slide this maintainer has been asking for help for years and dosent receive much in the discord. I also want quality code but don’t jump to demonize a volunteer especially when not many have jumped in to help

Did he ask for help in churning all the code for no reason? Rsync was complete software. It does not need features, it needs stability and merely maintenance. If the author used AI for small, well-reviewed maintenance changes, that would be okay. But instead he is making large and sweeping changes that are entirely uncalled for and cause breakage. If the maintainer is overworked, that is even more reason not to do th…

> Rsync was complete software.

It was (and is) not: rsync has over 300 open issues with bugs and feature requests.

Re: Please Do Not Vibe Fuck Up This Software

#158

A few years ago, the probability of such shit reaching the Hacker News home page was near zero, because regardless of the merits, here was not full of normies that could not understand when a behavior is unacceptable (I'm referring to the violence of the language of the issue). And now, here we are, surrounded by people that can't tell the most obvious things.

Maybe I'm getting too skeptical. I have a feeling increasingly many of the comments on HN and the GitHub issue are just bots ragebaiting other people (incl. the maintainer)...

[flagged]

Re: Please Do Not Vibe Fuck Up This Software

#159

A few years ago, the probability of such shit reaching the Hacker News home page was near zero, because regardless of the merits, here was not full of normies that could not understand when a behavior is unacceptable (I'm referring to the violence of the language of the issue). And now, here we are, surrounded by people that can't tell the most obvious things.

I think you’re looking at it through rose-coloured glasses. Controversial issues like this which fall outside regular bug reporting have always been submitted and became popular on HN. And developers are capable of such language, we have a reputation for being rude and even used to have a poster boy for it. Blaming this on “normies” (itself typically a dismissive word) is ignoring the problem has always been there and our responsibility in it.

Re: Please Do Not Vibe Fuck Up This Software

#160
post #36

I truly don't get it You have a rock solid piece of software used by an infinite amount of people and other services. It works fine, does it's job and just have some time to time updates due to minor bug fixes. Why do we need AI here? And more over, why people is saying "fork it and use the previous version". It should be actually all the way around, create a parallel fork younamethetool-ai and keep the OG untouched.…

> Why do we need AI here?

As several comments in the issue mention, it's up to the developers that contribute to an open source package to decide how they do it. Complaining on an issue tracker (apparently without proof) about AI ruining a piece of software is a form of "Open Source contributor abuse" discussed frequently on Hacker News [1]

https://github.com/RsyncProject/rsync/issues/929#issuecommen...

> The issue tracker is not a place for you to farm viral social media posts. Either report an actionable bug or fork it yourself. Venting about the developers choices is not productive.

https://github.com/RsyncProject/rsync/issues/929#issuecommen...

> @II-Paulus-II Stop. You know nothing. You have shipped 0 features by hand. No one has ever depended on your code. You are a finger-wagging "AI wrote this" type in an era where you hide in plain sight coasting on the moral high ground of writing toy projects and scripts from scratch. Can't ship, can't adapt, can't even realize that an issue tracker is not the place for this kind of attitude.

[1] https://news.ycombinator.com/item?id=43077833

Post reply on HN