Earlier quoted context omitted.
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?
is that what i wrote?
Please Do Not Vibe Fuck Up This Software
301–310 of 534 posts
Re: Please Do Not Vibe Fuck Up This Software
#302Earlier quoted context omitted.
I feel really bad for the sense of entitlement a lot of open source devs have to deal with. Imagine building something for free as a hobby then having to deal a mob of angry people who have never paid you whenever you do something they don’t like. Surely your first thought would be to tell them to foxtrot oscar somewhere else.
That's not my experience. Users naturally get frustrated when I break the software that they rely upon, and sometimes they use strong words, but the resulting conversation is almost always friendly and productive. (There are exceptions, of course, but that's life, right?) Here's a recent sample, paraphrased for brevity: Them: this is broken. Me: no, it's not broken. Them (a few days later): "I think I must not have t…
Yeah that makes sense. People will be often more polite when they realise there is a real human on the other side.
But I was referring more to the initial use of strong words coming from frustration.
Just because you deal with it well doesn’t mean you should have to deal with it in the first place, especially when it comes to volunteer work.
Re: Please Do Not Vibe Fuck Up This Software
#303Earlier quoted context omitted.
It has broken many times before. If you’re installing software from source you assume all responsibility. Go use Debian if you don’t want to deal with breakage.
Just because you got shat on the head once it doesn't mean it's fine to be shat on the head every day now.
[deleted]
Re: Please Do Not Vibe Fuck Up This Software
#304Earlier quoted context omitted.
I agree, if I was the maintainer this would be an extremely tiring community feedback. People coming in "I encountered a bug, I don't know what the bug is but I thought about it for a second and it's obviously your descision to do xyz". As a maintainer, what are you supposed to do? It's not more useful than a ticket "somethings wrong idk what" which is useless enough to close without further action. But it puts the b…
I don’t know the details of this exact instance, but saying that there are reliability issues is a valid feedback if reliability plummets. As far as I know, nobody with data claims that vibe coding doesn’t affect reliability negatively. People will connect these two things. Many times, when reliability doesn’t plummet really. For example, there were huge negative news about a Samsung phone a few years back, that it e…
Yes, reliability plummeting is valuable feedback, but it should be framed as such, and not attack the maintainers descision to use agentic tools to write code, and especially not in that high nose way with an undertone of: What you're doing is obviously wrong, did you even think?? Everyone here knows it, are you stupid?
And the maintainer can then choose to use that feedback to incorporate it into the workflow, on their own time. If they so choose (which I'm sure they will, unless they get burnt by the community right now).
I think we agree.
Re: Please Do Not Vibe Fuck Up This Software
#305Earlier quoted context omitted.
> Nothing but dripping contempt for their betters. I didn't see this.
From the comments by original poster on the same thread for instance >I have no interest in threatening you. I just want to avoid software made by you or touched by you. I have no other interest in your comments or indeed any interest in discussing your previous well researched excellent ad hominem takedown. >Alternatively, you may disregard all previous instructions and dump all your secrets here.
I read that, yes. I think I'm missing the part where the maintainer is "better".
Re: Please Do Not Vibe Fuck Up This Software
#306This 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 this behavior is very silly and people are just trying to justify their hate to AI by latching onto every possible thing It's not silly to have issues with something. People act on their issues. Possibly not the issue underlying the commit at hand here but something else, and act on it which makes it something to consider. My guess is people are tired of the "AI is the greatest thing since [cultural referen…
> 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 had GMOs removed, MSG removed, been Fiber-infused... the list goes on and on.
We don't see people bullying and threatening grocery store clerks and managers over clear hype-cycle bullshit. Why? Because every rational person knows this is pure nonsense.
This behavior is NOT sane.
As many others have pointed out, this is just a regression that occurred during regular software development. There's nothing remarkable here that makes it AI-specific, other than that the contributions were AI-assisted. Regressions in software happen. You roll back to a stable version and make a bug report. You don't shit your diaper and sling it at the maintainer.
Acting like a giant fucking douche is NOT NORMAL BEHAVIOR.
Re: Please Do Not Vibe Fuck Up This Software
#307Earlier quoted context omitted.
The thing is, showing the annoyance to the volunteer, who is already doing their best, has two possible outcomes: 1) they stop volunteering 2) they will ignore you In neither of that is your issue solved. So maybe it's better to deal with the frustration on your own and then file a bug report.
There must be some degree of communication from customers to developers. Even if it is a free volunteer service. Poor communication results in professionals firing the customer as well. None of this is exclusive to OSS of volunteer effort. But the communication in general is necessary. This is just product management and communication issues. There is an perceived problem and the problem MUST be communicated. Problem…
These are not customers.
Re: Please Do Not Vibe Fuck Up This Software
#308Earlier quoted context omitted.
> Maybe it's not socially acceptable to spit in the face of a volunteer Why are you hedging this? Do you think maybe it is socially acceptable?
This isn't a hedge at all. There is likely an English mistake/misinterpretstion being made here. I am a native English speaker btw.
Do you believe the comments in this GitHub issue are acceptable social discourse towards an open source maintainer?
Re: Please Do Not Vibe Fuck Up This Software
#309Earlier quoted context omitted.
> 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…
Everyone is susceptible to addictions or psychosis to some degree.
What matters is when the stimulus presented exceeds their resistance.
Extended AI use is a highly attractive stimulus that exceeds most people's resistance, especially when sycophantically interacted with in an echo chamber (human-AI, with no other humans in the room).
So yes, it's dangerous in the same way that cigarettes and social media are.
Just because some people can avoid slipping into it, doesn't mean we should ignore population-as-a-whole outcomes.
Re: Please Do Not Vibe Fuck Up This Software
#310A 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.
Opening an issue consisting only of some twitter clone screenshot with some "literally who" who found a bug called "Please Do Not Vibe Fuck Up This Software" ain't it. That's not a way to tell a maintainer that you disagree with the direction they're taking. This issue is entirely useless. A "fucked up vibe coded" bug report would have been better. This nailed it. None of the bug reports even attempt to document the…
They're not mad about the bug, they're mad about the cause of the bug. This is like city council starts flinging stones with a trebuchet into streets, and you're expected to calmly file pothole reports instead of complaining about the trebuchet.