Live data from Hacker News

Godot will no longer accept AI-authored code contributions

pcgamer.com

401–410 of 419 posts

Re: Godot will no longer accept AI-authored code contributions

#401

Earlier quoted context omitted.

Oh god. If you really believe you can vibe code an engine in 6 months I challenge you to do it. I think you'll find you've wildly underestimated what goes into an engine.

https://github.com/charlesrw1/MultiplayerFps , its pretty easy. And this is just my hobbyist engine Ive been solo orchestrating agents with. If you had a team of ~10 AI-enabled devs, you could easily reach feature parity with Unity in a month or 2.

> Build: Let your agent figure it out

I'm sorry for going off on a random hobby project, but doing this in a C++ project - even if it is a standard Visual Studio solution - is "putting your whole mouth into the salsa dip"-level rude IMO, agent access should not be a prerequisite to build code!

Re: Godot will no longer accept AI-authored code contributions

#402

Earlier quoted context omitted.

YES! "No AI" policies that are purely based on technical grounds make no sense to me. Bad PR's are bad PR's regardless of their source. Are we really in a situation where good code that solves a problem won't be merged because the person the person checked the "I used AI" box on the PR? Ban PR's that are too big, don't have a clear purpose, touch too many areas, etc.

It's really a question of how much time you're willing to spend sorting through spam. "No AI" might be a blunt hammer, but the people submitting slop aren't reading guidelines anyway, and it's easier just to reject it early. Frankly, I'm sure if people wanted to sneak in an AI generated code by carefully reviewing it and making sure it's targeted and well tested... I'm sure they could, but those people aren't the pro…

> Frankly, I'm sure if people wanted to sneak in an AI generated code by carefully reviewing it and making sure it's targeted and well tested

But this is exactly the point I'm making. If the code is carefully reviewed, targeted, and tested, then why make people have to lie in order to submit PRs?

Why not just say "Irresponsible use or agentic-based PR's will be auto-rejected"?

And that's not even mentioning that tools like Github Copilot can just act like fancy autocomplete. There are dozens (if not hundreds) of different ways to use these tools.

I guess I'm just really not sure how you can unequivocally forbid these insanely powerful tools when they are almost certainly going to be a large part of developer's workflows going forward?

Re: Godot will no longer accept AI-authored code contributions

#403

Earlier quoted context omitted.

> I personally wouldn't care if it was AI-generated or not, as long as the content fit the latter category. The problem is that a lot of AI contributions are lazily produced without review. Those that have been properly reviewed for correctness (tested to ensure actually working with no obvious undesirable side effects, tweaked where needed to be readable and understandable, fitting the other guidelines of the projec…

> The problem is that a lot of AI contributions are lazily produced without review. That sounds like a contributor problem. Not an AI problem. I still don't understand a "no AI" policy whose only purpose is to weed out bad PRs. You should be weeding out bad PR's regardless of their source. I don't see why treating a purely human-authored, but bad, piece of code should be treated any differently than an AI-authored on…

A tool that encourages bad behavior at scale is a bad tool. Blaming individuals for a collective problem leads to no improvements.

Re: Godot will no longer accept AI-authored code contributions

#404
post #167

Earlier quoted context omitted.

> I personally wouldn't care if it was AI-generated or not, as long as the content fit the latter category. It's pragmatic. Linus once said, the reason C++ is not allowed in the kernel is to keep the C++ people out.

Joke's on him, many Rust people are current or former C++ people.

> Switching to a more modern topic, the introduction of the Rust language into Linux, Torvalds is disappointed that its adoption isn't going faster. "I was expecting updates to be faster, but part of the problem is that old-time kernel developers are used to C and don't know Rust. They're not exactly excited about having to learn a new language that is, in some respects, very different. So there's been some pushback on Rust."

https://www.zdnet.com/article/linus-torvalds-talks-ai-rust-a...

Re: Godot will no longer accept AI-authored code contributions

#405

Earlier quoted context omitted.

> AI can be trained. I don't have access to a data center's worth of GPUs, unfortunately. You offering yours?

So when you said "AI cant be trained" you didn't mean "AI cant be trained" you meant that you personally can't? lol.

I'm saying that most people, even most programmers, don't have the facilities or inclination to train new models man. I've done it plenty of times and I absolutely don't recommend it.

Frankly I don't think you even know what the phrase entails.

Re: Godot will no longer accept AI-authored code contributions

#406

Earlier quoted context omitted.

> > The problem is that a lot of AI contributions are lazily produced without review. That sounds like a contributor problem. Not an AI problem. Ish. The tool is not doing the job fully, the contributor is not doing their task properly, checking for that, and fixing the issues. > I still don't understand a "no AI" policy whose only purpose is to weed out bad PRs. You should be weeding out bad PR's regardless of their…

Saying you didn't use AI when you did, regardless of the end product, is lying. What definition of the word lie wouldn't cover that?

If they are simply filtering out based on signs of AI, then there is no lie.

If they are explicitly asking “was AI used” then yes, there is a direct lie involved.

If there is no explicit question but you are including “lies by omission”, then be aware that there are many things people choose not to say that they would be unfairly judged for if they did state (gender details, certain parts of their history, etc) so that might not be a line we want to draw.

I'm not exactly pro-AI, in fact I'm avoiding it in DayJob to the point where I expect at some point I'll be given the choice “get with the program or leave” (I plan to leave at that point, preferably by my own choice though we'll see how heated the discussion gets!), but if there is a at least one human at the end of the process that is properly testing and cleaning everything up so there can be nothing problematic in the AI output that survives, is that really practically any different to a fully human created contribution?

The problem with AI contributions in the vast majority of cases is the lazy ones, especially considering the sheer number of them. Using signs of AI as a code/documentation smell when it comes to filtering contributions is fine, especially if you have up-front requested no such contributions be sent. Permanently blocking people who have sent obviously AI-generated contributions previously despite you asking them not to, is also fine just as blocking people who have sent in entirely human made contributions that break your other requests/rules is. But banning all AI use when if you can't tell if a good contribution did or didn't use AI aid somewhere in the process, is both a daft extreme and actually impossible (if you can't tell, how do you tell?!).

Re: Godot will no longer accept AI-authored code contributions

#407

Earlier quoted context omitted.

So when you said "AI cant be trained" you didn't mean "AI cant be trained" you meant that you personally can't? lol.

I'm saying that most people, even most programmers, don't have the facilities or inclination to train new models man. I've done it plenty of times and I absolutely don't recommend it. Frankly I don't think you even know what the phrase entails.

So again, you can train people but not AI? That's literally what you've said and now moving the goal posts in a way that makes no difference to what you said being patently wrong.

It's wild having to argue with people who say demonstrably untrue things and then refuse to admit that what they said was wrong.

Re: Godot will no longer accept AI-authored code contributions

#408
post #36

Just put it behind a paywall for PR prioritization or consideration, more payment to jump the queue. There, I solved FOSS sponsorship.

I honestly think that a 1$ “deposit” to submit a pr for new contributors (to be returned if the pr is merged) could help with a lot of OSS problems

Doesn’t even have to be merged, it’s for the privilege of even being considered to be merged into a popular library, one can always fork but to put stuff in a popular repo should be pay-walled henceforth

Re: Godot will no longer accept AI-authored code contributions

#409

Earlier quoted context omitted.

I'm saying that most people, even most programmers, don't have the facilities or inclination to train new models man. I've done it plenty of times and I absolutely don't recommend it. Frankly I don't think you even know what the phrase entails.

So again, you can train people but not AI? That's literally what you've said and now moving the goal posts in a way that makes no difference to what you said being patently wrong. It's wild having to argue with people who say demonstrably untrue things and then refuse to admit that what they said was wrong.

Yeah, real wild.

Re: Godot will no longer accept AI-authored code contributions

#410

Earlier quoted context omitted.

just because someone writes or wrote C++ doesn't make them a "C++ person", and "C++ people" are very much against rust

Only true Scots... err C++ people are against Rust, I see :>

more that, most C++ developers aren't "C++ people", the ones that are are a very vocal, but very small minority, though they're disruptive enough that some projects (re: the aforementioned linux kernel) elect to abandon C++ entirely just to avoid them
Post reply on HN