[flagged]
Godot will no longer accept AI-authored code contributions
81–90 of 419 posts
Re: Godot will no longer accept AI-authored code contributions
#82Interesting that on one hand the valuation of these AI providers is based on the assumption that all code (and everything else producing digital artefacts) will be written using AI in the near future, on the other hand almost all popular open source projects fight to keep AI contributions out. Hard to reconcile.
Personally I'm also experiencing a bit of AI hangover after using it a lot in my own open-source projects. I find it's a bit like taking drugs (not that I have much experience with that) in the sense that in the moment I'm using these tools I feel great and powerful, writing features in a span of hours that would've taken me weeks to write by hand. But inevitably some time later I will look at the code and notice all the subtle cracks and inconsistencies the tool introduced, and despair a bit at the mess.
I now plan to use these tools less for extensive feature development and more for planning, debugging and narrow refactoring where I can put very strict guardrails on them. I'd still say it accelerates my work but not by a factor of 10, more like 1.5-3 (which is still a lot) given the care you need to ensure what is being built is actually good. For what I really like these tools is that I need less mental focus to do coding, but on the other hand I have this new kind of fatigue of being in a constant chat loop with a machine and trying to get it to do stuff based on natural language, never knowing how it will interpret what I write and wrote before. In that sense, these tools don't feel satisfying, it's like operating a machine where you try to push some buttons to get it to do something but the internal wiring changes all the time so you never know exactly what a given button combination will do and you have to figure it out by watching the machine and constantly adapting.
Re: Godot will no longer accept AI-authored code contributions
#83Interesting that on one hand the valuation of these AI providers is based on the assumption that all code (and everything else producing digital artefacts) will be written using AI in the near future, on the other hand almost all popular open source projects fight to keep AI contributions out. Hard to reconcile. Personally I'm also experiencing a bit of AI hangover after using it a lot in my own open-source projects.…
> the moment I'm using these tools I feel great and powerful, writing features in a span of hours that would've taken me weeks to write by hand. But inevitably some time later I will look at the code and notice all the subtle cracks and inconsistencies the tool introduced, and despair a bit at the mess.
Very relatable. I wasted 2 weeks of full time effort earlier this year building a helper library with Sonnet. It was the first (and the last) time I vibe coded something. Once I was satisfied with it, I began using the library and within 2 days I was certain it was all for nothing. I will never get those 2 weeks back, but a lesson has been learnt.
Re: Godot will no longer accept AI-authored code contributions
#84Earlier quoted context omitted.
> I can't think of a functional reason for a no-AI policy Imagine morals.
That would be part of the non-functional reasons mentioned in the next paragraph.
> I can't
That makes much more sense now. The inability is completely on you, and you admit it at least.
Re: Godot will no longer accept AI-authored code contributions
#85Perhaps move comments to source posted yesterday? 30-jun-2026 "Changes to Our Contribution Policies" https://news.ycombinator.com/item?id=48733236 9 comments
Re: Godot will no longer accept AI-authored code contributions
#86Earlier quoted context omitted.
How they enforce it in every other project with the same policy, if the reviewer/maintainer suspects the pr is ai slope he closes it. That's it, it works fantastically well, I do the same even in my job
"suspects".... that sounds error prone. And I read it like "we don't want AI generated stuff unless we can't tell the difference".
exactly, I for example don't care usually about false positives, in the very uncommon case it happens the pr creator can discuss and prove he actually understood the problem, the codebase, the project policy and how to explain his solution actually could work.
Re: Godot will no longer accept AI-authored code contributions
#87Earlier quoted context omitted.
Interesting initiative. What are the guiding reasons behind these lists? I can't think of a functional reason for a no-AI policy: if it runs, it runs, regardless of who or what made it. Also, even if you avoid AI-generated slop, you can't really avoid the human-generated or human+AI-generated slop that passes your filters. Still, I can definitely think of good non-functional reasons: provenance, accountability, proof…
Please define "if it runs, it runs"?
If you have some requirements/specifications, and the piece of code fits them, then it runs.
Alternatively, if you have some vague idea [1] about what you expect to see/have, and the running code satisfies that idea, then it also runs.
Obviously, there are plenty of non-functional specs (e.g., security, cleanness, readability) that a code should probably fulfill before one finds it acceptable, but these are also not somehow impossible for state-of-the-art models to satisfy.
[1] Vibe, if you prefer, tho I dislike the term. Another related term is eyeball estimation.
Re: Godot will no longer accept AI-authored code contributions
#88...the influx of contributions authored or submitted by AI is sapping the projects' maintainers of their willingness to confront the "already tedious" work of reviewing pull requests.... To me this seems a core issue: PR reviews for most people feel tedious and this has been the case way before AI already. Don't get me wrong, slop is slop, no matter if AI or entirely human-fabricated. But just like AI-assisted coding…
No, reviewing PRs in general is a delightful process. The tedious part is in the initial triage when the PR comes from a previously unknown submitter, and you cannot be sure what is the intention of the submitter, what is their technical level, whether they are talking out of their ass or not.
It's basically the same issue as spam in emails. It was bad before, and automation made it a zillion times worse.
Re: Godot will no longer accept AI-authored code contributions
#89Interesting that on one hand the valuation of these AI providers is based on the assumption that all code (and everything else producing digital artefacts) will be written using AI in the near future, on the other hand almost all popular open source projects fight to keep AI contributions out. Hard to reconcile. Personally I'm also experiencing a bit of AI hangover after using it a lot in my own open-source projects.…
> the moment I'm using these tools I feel great and powerful, writing features in a span of hours that would've taken me weeks to write by hand. But inevitably some time later I will look at the code and notice all the subtle cracks and inconsistencies the tool introduced, and despair a bit at the mess. Very relatable. I wasted 2 weeks of full time effort earlier this year building a helper library with Sonnet. It wa…
Totally! The feeling of using AI to create something not fully productive is similar to the "just one more turn..." effect when playing a Civilization game. Even when you realize it's a waste, it's hard to stop, because the next dopamine hit is just around the corner.
Re: Godot will no longer accept AI-authored code contributions
#90Interesting that on one hand the valuation of these AI providers is based on the assumption that all code (and everything else producing digital artefacts) will be written using AI in the near future, on the other hand almost all popular open source projects fight to keep AI contributions out. Hard to reconcile. Personally I'm also experiencing a bit of AI hangover after using it a lot in my own open-source projects.…
> the moment I'm using these tools I feel great and powerful, writing features in a span of hours that would've taken me weeks to write by hand. But inevitably some time later I will look at the code and notice all the subtle cracks and inconsistencies the tool introduced, and despair a bit at the mess. Very relatable. I wasted 2 weeks of full time effort earlier this year building a helper library with Sonnet. It wa…
[deleted]