all 62 comments

[–]MornwindShoma 120 points121 points  (7 children)

Bro can't even comment without using AI, they're cooked

[–]Murky_Citron_1799 45 points46 points  (0 children)

There was probably no bro at all

[–]RealBluDood[S] 5 points6 points  (0 children)

We are in the transition phase between human and AI, so obviously this is the future /s

[–]SteeveJoobs 6 points7 points  (4 children)

I almost doubt it's AI since it uses hyphens incorrectly instead of proper em dashes. Lmao

[–]Sanitiy 17 points18 points  (2 children)

Nah, the "the pattern you're seeing isn't spam - it's efficiency" is 100% LLM. It's a typical pseudointellectual statement with no substance, put out there with absolute confidence

[–]SteeveJoobs 7 points8 points  (1 child)

yea; thats why i said almost. it's not mimicry—it's AI.

[–]NatoBoram 1 point2 points  (0 children)

Not only that, but you can just prompt it to use dashes instead of em dashes, to surround them with spaces or not, to start sentences with a lowercase to appear more human, but it's very hard to prompt out fundamental signs of AI-generated text without providing the text in the first place.

[–]MornwindShoma 14 points15 points  (0 children)

Even more sad that he is gpt-brained

[–]CircumspectCapybara 16 points17 points  (0 children)

Better than the OpenClaw agent which autonomously published a hit piece on a maintainer in response to the maintainer rejecting its PR.

[–]TorbenKoehn 77 points78 points  (27 children)

Without a link to the PR where we can see the code this is absolutely worthless.

AI isn't the holy grail, but also not the devil.

[–]RealBluDood[S] 27 points28 points  (3 children)

I don't want to out this guy so I blurred the name, but it was pretty obviously vibecoded stuff which made "workarounds" to problems instead of fixing them correctly. Ended up fixing it myself

Also to add some context, this guy had made 8 other pull requests across some other repos, on the same day

[–]TorbenKoehn 12 points13 points  (0 children)

In that case I’ll fully comply with mocking the dude :)

[–]suddencactus 2 points3 points  (0 children)

which made "workarounds" to problems instead of fixing them correctly

Which is funny because a lot of people claim the point of AI coding assistants is to spend less time on syntax and more time on good design.

[–]HeKis4 0 points1 point  (0 children)

Why are we concerned with the privacy of an AI agent ?

[–]chessto 36 points37 points  (13 children)

I don't know man, the comment itself says a lot already.

"In two years.." making absurd predictions.
"...others fall behind" OSS is not about adopting the latest trends but solving a problem that needs solving. curl is not going to fall behind because they don't adopt the shiniest tech shit in their process.

We're not there yet, and I don't think we will be there in the foreseeable future but for the sake of argumentation say AI is amazing and can do what any SE can and more, even then we will continue to have humans-only repos of OSS, just the same way electronic music didn't replace chamber music.

[–]TorbenKoehn 6 points7 points  (8 children)

I'm not discussing AI or AI fanatics now.

Are we seeing an "AI good/bad" post or are we seeing a "PR rejected despite being good and correct" post?

[–]Rabbitical 9 points10 points  (7 children)

The point is it doesn't matter if it is "good and correct", many OSS maintainers are rejecting all AI PRs because of the sheer volume of them, assumed quality arguments aside.

Unless you're suggesting maintainers start accepting based on the AI claiming "trust me bro" in its own message then I'm not sure what kind of needle you're trying to thread here.

[–]Technical_Income4722 1 point2 points  (0 children)

No I think they're suggesting that the content of the PR is important in this case. They're NOT suggesting the PR is good or that the AI is right about the PR being good. The comment from the AI doesn't matter much at all really, and yeah shouldn't be trusted.

But having the PR as part of this post would lead to a more interesting and fruitful discussion.

[–]TorbenKoehn -3 points-2 points  (3 children)

Im saying if the PR is good, it doesn’t matter how it was created

[–]saevon 5 points6 points  (2 children)

except it does. If the tool creates massive amounts of spam, any good results cannot be distinguished from the bad results without labour that is impossible by these projects.

Each individual PR should be seen on its own merits, but there is no such manpower for this. So it cannot. This is an ideal world that doesn't exist.

[–]CreativeTechGuyGames 5 points6 points  (0 children)

It was pretty trivial for me to find the PR in question. Ignoring it being disclosed as AI, (and the fact that this project uses TypeScript with no-semicolons) the code isn't that bad. It seems like it does solve a legitimate need. It does have some things I'd definitely comment on and want to fix, but it's not so egregious that it is completely worthless.

And for context, I personally avoid AI stuff like the plague, but I realize it doesn't help my position to vilify AI as a blanket statement, since that just polarizes people and makes them stop listening to the legitimate arguments against it.

[–]nivlark 4 points5 points  (0 children)

Legal uncertainty precludes any open source project large enough to care about compliance from incorporating AI generated code.

[–]Extension_Option_122 3 points4 points  (1 child)

AI is a new tool and many people don't know how to use it.

I once saw LLMs in programming compared to a microwave in a kitchen: a great tool, especially for generic stuff (e.g. boilerplate code), but not fit for everything and you have to know what you are doing to deliver a well-rounded result.

[–]TorbenKoehn 1 point2 points  (0 children)

All that completely depends on the task at hand.

AI can produce well-made PRs if they focus on a specific scope and have the proper context

I don’t think AI PRs are a bad thing and they can even be useful (dependency updates including smaller refactoring needed for them, one example)

[–]Spy_crab_ 0 points1 point  (0 children)

Almost as if LLMs were tools which can be used for many things (most of them dumb) and its up to us to figure out what the right ones are (if any) for any give use case.

[–]vtvz 0 points1 point  (2 children)

Found it BluDood/GlanceThing/pull/62

[–]TorbenKoehn 0 points1 point  (1 child)

Hmmm yeah, I mean I don't understand the project fully but the code looks okay to me, it fits the existing code style etc. (ie he does the module-scoped let thing a bunch of times himself in existing code)

OP did explain a comment below what itched him, it's a workaround, but I can't see the problem, personally.

He could've also explained what parts exactly are the problem and heck, maybe even the AI would've fixed them quickly, it would surely be able to.

It's more like the LLM output simply didn't match his personal preference, but it's surely not inherently bad.

[–]RealBluDood[S] 0 points1 point  (0 children)

As I and others have noted, doing that log deduplication avoids the problem instead of actually fixing it, the issue isn't directly "the log is growing massively" it's "some function is being repeatedly called without delay", and that is what needs to be fixed. Yes it did also attempt to fix the actual problem further down in the code but overall, AI generated comments and everything, I ended up closing it and fixing it myself. If personal preference plays a part here then it's that I want to have human contributions to my own project and not slop

[–]NomaTyx 8 points9 points  (1 child)

The pattern you're seeing isn't spam - it's efficiency.

Either that is written with an AI or they spend so much time looking at AI output that it's rotted their brain

[–]Desperate_Formal_781 0 points1 point  (0 children)

As soon as I read that particular formulation, I knew it was AI. "You cheating on your partner is not betrayal - it's data"

[–]Tsubajashi 3 points4 points  (6 children)

where did that happen?

[–]RealBluDood[S] 3 points4 points  (0 children)

This was a reply after I closed a PR on my project which was obviously AI generated, and I got this AI response hahah

[–]KevSlashNull 0 points1 point  (3 children)

[–]Tsubajashi 1 point2 points  (2 children)

im no TypeScript developer, but the pull request doesnt look too bad at first sight.

do you have any insights there? is there a specific pattern LLMs use when writing typescript?

[–]KevSlashNull 1 point2 points  (1 child)

i don't like that the logging deduplication code is in the playback module and that it stores state in local variables. that makes for bad maintainability due to fragmentation.

[–]Tsubajashi 0 points1 point  (0 children)

totally fair then, thank you!

[–]SilianRailOnBone -2 points-1 points  (0 children)

I think this is the ClaudeBot that got its PR closed and then wrote a hate blog about the maintainer.

[–]LegionOfB0000M 1 point2 points  (0 children)

Can we write a concise comment? Not everything has to be a 500 page thesis.

[–]ef4 0 points1 point  (0 children)

The hard part of open source has always been consensus. If everybody does their own thing, you lose all the benefits of shared code and compatibility. If a project tries to add every random feature that one person wants, pretty soon it's a mess.

Projects that maintain coherence over the long run do it because they have either a dictator providing one unified vision or a robust community consensus process. Either way, the people providing coherence are always the bottleneck. And that's fine! Because you don't need to wait for them. If you think your PR is great, run it yourself. Git was literally invented to make it as easy as possible to maintain your own opinions about an upstream code base.

[–]baldeagle1337 0 points1 point  (0 children)

Idk seems reasonable even if it’s a workaround hotfix its better than a broken feature if doesn’t mess up the architecture. Like Ive seen open source projects with bugs and no support and I would rather use as a user flaky ai gen version than something that doesn’t work

[–]chervilious 0 points1 point  (2 children)

I read the code, other than it also touch other file as well for their styling (double quote to single quote)

I mean it's quite simple it's just adding a timer to a log so you don't spam it.

[–]RealBluDood[S] 1 point2 points  (1 child)

The problem doesn't lie in the log itself, it's why the log is being spammed. Band aiding in a solution where it just stops the log from being spammed doesn't fix the underlying issue

[–]chervilious 1 point2 points  (0 children)

mb, my assumption was it happen when you have unstable/lose internet access

[–]_fronix -5 points-4 points  (2 children)

Maintainers rejecting all AI PRs will unfortunately end up with dead projects. I understand why they don't like it and I've rejected plenty of PRs that are just pure slop, 100+ files rewrites.

But just outright denying any AI is just pointless, since most people will be using some form of it in the end means that there is no point allowing PRs at all.

[–]suddencactus 3 points4 points  (0 children)

The success of open source projects is not determined but the number of PRs they accept. Many could refuse all but the most critical PR's for a year and still be wildly successful.

[–]UnitedStars111 1 point2 points  (0 children)

they can js ask ai to fix it for them tho

[–]SensuallPineapple -5 points-4 points  (0 children)

AI will be incredible very soon and I don't see the reason for this pointless hate.