Live data from Hacker News

Please Do Not Vibe Fuck Up This Software

github.com

351–360 of 534 posts

Re: Please Do Not Vibe Fuck Up This Software

#351
post #321

Earlier quoted context omitted.

[flagged]

The target of the issue title is pretty clearly the maintainer. They’re the one being told to stop using AI. I guess this answers the question of whether you think maybe it’s ok to spit in the face of open source developers.

“Maybe don’t do that?” does not mean “I support you doing that” no matter how unfamiliar you are with it as an idiom.

“I cut my finger with the kitchen knife”

“Maybe don’t hold it by the blade”

It’s something along the lines of sarcastic and deliberately unhelpful because “duh, of course don’t do that”.

Re: Please Do Not Vibe Fuck Up This Software

#352
post #153

Earlier quoted context omitted.

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.

Autonomous agents are different. Claude should fork the repo because it is a new maintainer trying to take over a project. Doesn't matter if the OG maintainer is under illusions.

There’s so much to unpack here, but let’s say I grant your premises that AIs are equivalent to people and Claude is making its own decisions about the project and the OG maintainer has ceded control of the repo to Mr Claude.

I don’t, but let’s assume for a moment.

It’s still up to the current maintainer to pick additional or replacement maintainers, and it would be bonkers to expect the new maintainer to fork the repo to implement their changes.

Open source projects change their maintainers all the time.

Re: Please Do Not Vibe Fuck Up This Software

#353
post #321

Earlier quoted context omitted.

The target of the issue title is pretty clearly the maintainer. They’re the one being told to stop using AI. I guess this answers the question of whether you think maybe it’s ok to spit in the face of open source developers.

“Maybe don’t do that?” does not mean “I support you doing that” no matter how unfamiliar you are with it as an idiom. “I cut my finger with the kitchen knife” “Maybe don’t hold it by the blade” It’s something along the lines of sarcastic and deliberately unhelpful because “duh, of course don’t do that”.

[deleted]

Re: Please Do Not Vibe Fuck Up This Software

#354
post #321

Earlier quoted context omitted.

The target of the issue title is pretty clearly the maintainer. They’re the one being told to stop using AI. I guess this answers the question of whether you think maybe it’s ok to spit in the face of open source developers.

“Maybe don’t do that?” does not mean “I support you doing that” no matter how unfamiliar you are with it as an idiom. “I cut my finger with the kitchen knife” “Maybe don’t hold it by the blade” It’s something along the lines of sarcastic and deliberately unhelpful because “duh, of course don’t do that”.

This doesn’t seem related to my comment. Did you mean to reply to me upthread?

Saying ~“maybe it’s not ok to do but ” is nothing like your example and does imply it’s acceptable to the speaker to sometimes do that thing.

But we’re past that now because the person I was discussing this with has gone ahead and clarified that telling an open source maintainer to please stop fucking up isn’t an angry comment.

Re: Please Do Not Vibe Fuck Up This Software

#355
This is brigading and it is not ok. It doesn't matter what the hot-button-topic-du-jour is. Oil? Think of the children? AI? Doesn't matter, they get to vent rage on a random subject at a Random Person On The Internet.

I don't know what sets this kind of thing off, maybe it's not predictable, but it's never ok.

I'd like to hope in a few years those people will look back on their participation in this particular brigade sheepishly; but sadly it's more likely they'll have forgotten about it by morning.

Re: Please Do Not Vibe Fuck Up This Software

#356
post #342

Earlier quoted context omitted.

[flagged]

That’s exactly what I was calling out. Customers pay money for goods and services. They thus get a bunch of social, ethical, and legal positions in terms of their relationship with the seller. Rsync is an open source project that its maintainers put onto the Internet. People who use it are not customers, and they do not have the right to expectations around how the maintainers will change the software or change how t…

You've never had a customer in your professional setting who didn't pay money for goods and/or services? Yet it was very important for your boss (and therefore you, as a programmer) to service their every whim?

Customers are customers. Whether they're paying or not. Not all customers are worth servicing (even with infinite money offered, "firing a customer" is important to keep the community in check).

But this isn't a situation where the RSYNC maintainer should fire the customer. There's a LOT of backlash to this release. Even if this one particular customer is a bit of an ass, there's plenty of good users in that 90+ comment chain (hundreds now?) where this regression has clearly struck a nerve.

Re: Please Do Not Vibe Fuck Up This Software

#357
post #306

Earlier quoted context omitted.

> My guess is people are tired of the "AI is the greatest thing since [cultural reference]" being forced down their throat and grasp at every straw to combat it, which is a sane response in my opinion and should be taken into account. Let's engage in some parallelism then This happens with literally everything in our society. Right now, every single food product seems to be infused with protein. In the past, they've…

>regression happens Yes, but some should absolutely be caught with a robust test suite, especially if it is not an edge case. When was the last time there was a breaking regression in SQLite again?

What does your strawman argument about a hypothetical regression in SQLite have to do with this? What would a regression in the Windows Calculator have to do with this? What does your whataboutism prove here? Nothing.

A mistake was made. There are well worn paths for fixing the mistake. Acting like a giant fucking petulant pissbaby is not the critical path to getting things fixed and is deeply corrosive to the positive collaborative environment we’ve all spent decades building within shared, community software.

Get the fuck over yourself.

Re: Please Do Not Vibe Fuck Up This Software

#358
post #294

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 thi…

I think people are very justifiably angry that a very stable, well trusted tool, has started to immediately go downhill. The Linux Mint Timeshift tool has an issue open documenting a number of regressions that are currently open on the rsync issues page, that were only introduced post-vibecoding ( https://github.com/linuxmint/timeshift/issues/548 ), one of those links goes to a larger aggregate of bugs reported downs…

> I think people are very justifiably angry

That may or may not be true, people are justifiably (or not justifiably) angry about a lot of things all the time.

But this was very obviously a brigading attempt. It's a form of online bullying. If it had been about whether the maintainer liked striped socks, nothing else about this would have changed.

Later on the brigade can claim "oh we had a justifiable grievance" to sooth their souls, but what actually happened is what actually happened.

It's all a bit silly and childish.

(To be sure: the balance of fao_'s statement is well reasoned. It's the brigade who are being childish, and I don't think they should be rewarded for that. )

Re: Please Do Not Vibe Fuck Up This Software

#359

Earlier quoted context omitted.

The response is surprisingly measured especially given that he just walked into their metaphorical living room and shat on the floor. Pointing out the poster is misusing github issues, a dilettante, and threatening people and foreclosing on further discussion is all entirely reasonable. Lots of people in the comments but did you attend to who was an actual maintainer for that repo or did you just assume that the peop…

You misunderstand. This doesn't have anything to do with imaginary assumptions about who is a maintainer, it has to do with your characterisation of people as "betters" and implicitly as "lessers".

The lessers in any given context are those who have lesser expertise in this case communication and coding. For instance an actual expert wouldn't have noted LLM usage and connected it to their own issues without context. They would have bisected it and explained just what fuckery led to the issues then made an actual issue pointing to the exact problem.

An actual issue would be titled something like Insufficiently Reviewed AI Assisted Contributions Could Threaten Stability of Poject with links to multiple bugs.

Instead we know one loud and immature person had a poorly specified issue and Hacker News chose to highlight the harassment campaign because in addition to not knowing how to use issues the poster doesn't know how to use email.

Post reply on HN