381–390 of 419 posts
"If your feedback on PRs is just being absorbed by a machine and not going towards mentoring a potential future maintainer, it becomes much harder to justify spending your free time on PR review," the Foundation said. That is to the point!
zig's 'contributor poker' is sounding more and more prescient.
Earlier quoted context omitted.
For many years, it's been difficult to build game engines. It's never been easier today. A half-decently funded startup team could get to Godot feature parity within 6-12 months. There's no VC in games anymore (especially not middleware), so it's less unlikely, but they don't have a moat on features. When you go to invest in an engine. One with Claude Code natively infused and another that says "meh" to AI. Which wou…
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.
Earlier quoted context omitted.
I am struggling to understand the exact content of your message. I believe it's that Godot is unserious. Okay? Game engines serve a niche much smaller than broad consumer apps or SaaS platforms. Seems like a dunk I don't quite understand. It's a game built in Godot that runs on mobile (a mobile game). Godot is C++, there is no porting of engine to run on mobile? Slay the Spire 2 is built in Godot and has 500k concurr…
I interpreted your comment "Godot mobile app work" to mean you worked on porting Godot itself to mobile, which I then checked and found that it did actually happen https://godotengine.org/article/gabe-stable-release/ If Godot for Android is unrelated to you then I misread. But I still find it hilarious conceptually, unrelated to you, that Godot is spending resources on porting itself to phones while it has so many se…
And, since the Godot IDE is, itself, an app written in Godot, porting to mobile is almost free. More a question of tweaking than rewriting. That's the same reason there's a version of Godot runnable in a browser... it's a consequence of Godot allowing webapps as build targets.
Earlier quoted context omitted.
Let me tell you a story: I use agents at work. Not to add more useless features, not in a let-loose way, not so that I can slack all day but to produce better output. Think performance optimizations, security fixes, better use of underlying frameworks, produce better documentation, get useful hints from the code base, that kind of thing. In a word, to produce objectively better software. that is my honor: giving the…
You should have been fired for cause, because the way you chose to work exposed your employer to substantial liability due to the “copyright laundering” nature of LLMs. But you prioritized feeling good over everything else. You’re a sociopath and you should be treated as one—a bad-faith actor only out for themselves, who cannot be trusted to collaborate within agreed-upon limits because you don’t think rules apply to…
Earlier quoted context omitted.
Dingdingding, we have a winner. The main use of such a policy is to be able to just close those giant wall-of-text PRs and have something to point to when people start to scream it's not fair.
Why is a policy necessary. you were never entitled to have your pr merged in the first place? If pr wasn't reviewable pre AI I'd expect it to be closed or ignored too
Earlier quoted context omitted.
I interpreted your comment "Godot mobile app work" to mean you worked on porting Godot itself to mobile, which I then checked and found that it did actually happen https://godotengine.org/article/gabe-stable-release/ If Godot for Android is unrelated to you then I misread. But I still find it hilarious conceptually, unrelated to you, that Godot is spending resources on porting itself to phones while it has so many se…
An important compilation target for Godot is mobile, since it's obviously a very large games market. And, since the Godot IDE is, itself, an app written in Godot, porting to mobile is almost free. More a question of tweaking than rewriting. That's the same reason there's a version of Godot runnable in a browser... it's a consequence of Godot allowing webapps as build targets.
A long road does not sound like something almost free
It's a fair policy. Getting those verbose, AI-authored walls of text is very annoying, especially when you're expected to thoroughly review it. It's like a denial-of-service attack on the human mind. I can only imagine how frustrating this can get in open projects that get a lot of contributions. However, I don't think this will discourage AI-based coding at all. In fact, I see two potential outcomes of these policie…
In my day job, I do a lot of AI coding but almost never have Claude actually create the PR titles or descriptions for me. It produces too much content, and the justification/background sections are often not quite right. Most PRs to me are not coming out of nowhere anyway, rather they're "here's the linked issue, I started out addressing it by doing X and Y, but then Y got hairy so I switched to Z, hope that makes se…
Earlier quoted context omitted.
As a professional developer that's using these tools professionally and worked on multiple game engines and even written a few of my own... nope. Sorry, just, that's so much hype not grounded in anything. I'm guessing your job is to promote this stuff based on that being your purpose of going to GDC? Also, you're really misunderstanding why people use Godot in the first place. They've always been way behind Unreal En…
> that's so much hype not grounded in anything. Not grounded in anything ? Really, anything ? There's no evidence you've seen in the last three years that has had any impact on what you think is possible with AI coding? I'm not a game dev by trade, I am AI researcher turned AI engineer (not the "AI engineer" of the modern era, like getting ML deployed in prod). That being said, I have tried and failed to make plenty…
I actually do use them (daily), and I do find them to be useful. I even bought a couple books about how to implement them, and my own current app has an MCP server I've built. I also find them to be overhyped and not particularly essential (if I had to choose one to take to a desert island, I would take a good IDE over a good AI, for example). The way I currently see them is they make things more convenient, but it doesn't really expand what's possible for me, and that convenience can come at a profound cost (some of which we're just now starting to see). I already enjoy coding, so the convenience of not having to code is not that big of a win for me, and when you factor in the extra factors I don't even think it makes me go that much faster. (I either have to correct its outputs, or spend extra time understanding them, or the codebases become unwieldy and I've DEFINITELY seen that. On average AI code seems to be about 2-3x more verbose than what I would write). I can see why someone that can't code (or doesn't want to) would find them to be amazing, but I also think those people are not in a great position to judge the outputs, which is still pretty necessary and probably will be for the foreseeable future.
I think a common thread with AI use is it seems amazing when you're asking it questions about fields you're not an expert in (I like to ask ChatGPT questions about biology for instance), but it seems very much not amazing when you ask it questions about fields you actually are an expert in.
> Where's my inference coming from? The idea that you've conflated that AI coding by its very nature needs to be buggy and unstable. I wish you luck on holding the line as it slips past us on an exponential curve.
See, but that's what bothers me about these conversations in general, people just go "look at number go up!" like you can take any trend and just keep growing it forever. Or people make really bold claims with no evidence like your "you can vibecode an engine in 6 months" claim. It's hard to even _learn_ all the features of a mature game engine like Unreal Engine over _multiple_ years, and to do so would require at least being partially fluent in multiple different very different domains (art, animation, level design, shaders, workflows, about a trillion 3rd party tools, etc.) How could you vibe code something that quickly when even experts probably know about 15-25% of the feature set? Like how can you prompt an AI to build features you don't even understand? Also these engines evolved over a long period of time, so there are so many micro decisions and customer feedback loops that are completely opaque but important and are embedded in the code. The code in many engines contains decades of important knowledge!
I'm not swayed by the "exponentials" argument because past results do not guarantee future performance. I'm basing my opinions on what I've seen in my job and my personal work, and what I've seen is they're a boost, but not to the degree being sold and I'm kind of sick of people telling me that I need to be on board with the hype train or get "left behind". AI is not that hard to prompt, I don't view that as a real skillset, so to me I can either continue to bet on my own skills and intellect and hope they still hold value, or I can just get out of the industry entirely because my role would be entirely pointless. I would rather bet on myself even if I'm wrong, because all becoming dependent on it is going to do is degrade my skillset and my intellect, and if I'm right, well, honestly it's not particularly hard to train up on current AI harnesses or whatever compared to learning a skill (my computer science degree took 4 years -- learning Claude took a day. In what universe is knowing how to use Claude a marketable skill?)
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.
The weird thing though is I see comments like this all the time, and I've yet to see anyone come back a month later as a billionaire so.. I'm going to keep my skepticism for the moment.
As an aside, bragging about lines of code as the first thing in your repo is a very weird flex. Lines of code are a cost, not an achievement, you (or your AI) has to maintain them and the more you have the more it costs.
FWIW good on you for making a thing, my goal isn't to trash your project, but from my perspective this does not look like a serious competitor to any game engine; it reminds me of projects I've seen from college students before AI (I don't meant that as an insult, I just don't find this as compelling evidence for your argument)