Live data from Hacker News

Please Do Not Vibe Fuck Up This Software

github.com

111–120 of 534 posts

Re: Please Do Not Vibe Fuck Up This Software

#111

Been thinking of this mental model held by some "oh ai coding is always bad etc etc" (fair we all allowed opinions). But why are we okey with colleagues making from time to time terrible blunders (hey we all human ). But when ai makes mistakes its a sweeping judgment of "oh ai coding is terrible". We seen to not include all the amazing code they do right and security bugs they do find.. I feel if it was a human or co…

AI mistakes are due to pure laziness and incompetence that appears well done. There’s a big difference between that and a genuine mistake from a knowledgeable person.

Re: Please Do Not Vibe Fuck Up This Software

#112

Can GitHub add a tag to repositories that says "probably vibe coded" or "ai code detected"

would you argue for an 'unsafe code' tag too, if it's attached to repos with C/C++?

So all the other languages are safe now?

Re: Please Do Not Vibe Fuck Up This Software

#113
post #63
post #59

Earlier quoted context omitted.

wtf is this comment section? The author of these commits were tridge & claude. What does tridge have to do to convince the open source community that he might be a legit programmer & have a clue? Samba? Whats that? Rsync? Never heard of it. Tivo? No clue (maybe more Australian context here than others, but still). Even the comments on the github issue, are totally devoid of the context that this is a very senior open…

[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.

Re: Please Do Not Vibe Fuck Up This Software

#114

Earlier quoted context omitted.

The "swarm behavior" is mostly an illusion created by your mind. HN is just a bunch of people and bots.

Yep a bunch of people who often exhibit swarm behavior.

By this logic, will you just start calling yourself "hypocritical Karl", as you clearly belong here? ;)

Re: Please Do Not Vibe Fuck Up This Software

#115
post #4

> 26k code changes in 2 months..... rsync was 67k LOC as of 236417c (latest not obviously vibecoded commit it seems?).[1] Wow. 1: https://github.com/RsyncProject/rsync/issues/929#issuecommen...

Well to look at the last of that list. It added 134 - 3 lines to the project.

Of which, the actual change was

    -        __m256i mul_one;
    -            mul_one = _mm256_abs_epi8(_mm256_cmpeq_epi16(mul_one,mul_one)); // set all vector elements to 1
    +        __m256i mul_one = _mm256_set1_epi8(1);
and the rest was testing that fix.

Re: Please Do Not Vibe Fuck Up This Software

#116
This whole brigading is bizzarre and some people are behaving like irrational animals. I potentially understand the motivations that might bring one to want to "win" this battle but this really isn't it - it just makes you sound like a fanatic.

It takes 5 minutes to search for "regression" on the issue page and go through the 17 results. There are potentially even more on the tracker used prior to github.

I think this behavior is very silly and people are just trying to justify their hate to AI by latching onto every possible thing, seemingly forgetting that before AI people did mistakes as well.

If you have proof that AI involvement in rsync has lead to a significant increase in open issues please show it to me - I'll be happy to change my mind.

Re: Please Do Not Vibe Fuck Up This Software

#117
post #63

Earlier quoted context omitted.

[flagged]

Those posts may not have been visible to everyone. The posts you're referencing are hidden for me behind a link "33 Remaining Items (load more)". Without the update, I didn't know to go look for them. And honestly I noped out of scanning the entire comment thread by about #5 or #6... I could tell there was nothing productive in the remainder of the comments.

Actually it is, someone compiled allll the actual bug reports tracing back to AI:

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

Re: Please Do Not Vibe Fuck Up This Software

#118

Earlier quoted context omitted.

> this is a very senior open source contributer who has maintained this project since he came up with the diff algorithm during his Phd People change. You can be Linus Torvalds for all I care, if one day you wake up and start pushing 9000 line commits created by LLM and with regressions, you're not that person anymore.

But DID anything change? Of course I know that some people can just becoming psychotic out of nowhere. But why would I assume it?

According to the thread rsync broke for incremental backups and increases the cpu load heavily. The whole thread only started because people noticed regressions and were wondering what happened.

Since I quite a few users are using distros that won't update for a while it gets even better: this trend may continue and as soon as the update actually happens we'll be so far down the road that it will be too late to take a step back and reconsider due to the delayed feedback. This is pretty much about the few people _already_ having issues with it.

That being said, if the creator wants to use AI to work on the project they are free to do so. I just hope nothing of value is lost because of it.

P.S.: If you stop writing by hand and start delegating - to AI or other people - something has changed. There shouldn't be any discussion about it. Delegation is different than writing it yourself.

Re: Please Do Not Vibe Fuck Up This Software

#120
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.
Post reply on HN