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.

▲

maiybe 3 hours ago | parent [-]

Well, this is fundamentally where we end up disagreeing. Within the timeframe of a single mobile app development cycle, the entire coding infrastructure of the world changed. Our collective day-to-day coding experience has morphed within 15 months.

Here, you're making a negative argument, it "can't" be done. Maybe. Historically, correct. I prefer to image what could be done. As insane a statement as it sounds just 15 months ago, a small dev team could get it done, I'll stand by that. Framing is up to you, to each their own!

▲

anonymousab 2 hours ago | parent | next [-]

Even getting through the discussions and negotiations with the 3 big game console companies to support their platforms can eat up so much of your time window. You can't really vibecode your way out of that - though I suppose you could generate your email responses or an AI meeting participant and risk blowing up the business relationship.

▲

overgard an hour ago | parent | prev [-]

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 Engine and Unity on flashy features, that's not their value proposition. A lot of churn on half baked slop features would be counter to why people want to use it. Developers in a stressful industry want tools they can trust, not buggy unstable things that are constantly changing out from under their feet (a lot of teams freeze their engine version per-project for this very reason).

	▲	maiybe 27 minutes ago \| parent [-]
		> 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 of games over the years. Every mistake in the book. Making my own engine, trying to do 3D game as first approach, making mobile apps 2010, using Unity for personal projects, switching to Godot. I'm not at your level in game dev, but I've seen plenty at scale. > I'm guessing your job is to promote this stuff based on that being your purpose of going to GDC I'm not an AI hype maker, I'm a stunned observer. A person who has said "no way" AI will impact coding for the last 10 years. I am watching evidence in front of my very eyes and my workflow and simply adapting to the reality on the ground along with reasonable projection of capabilities into the future (based on velocity and reasonable assumptions). I don't need to convince you of anything, but I'm confident your beliefs won't hold up against the stockpile of evidence gathering now and in the near future. Since you took a swing and miss on who I am, I'm going to guess that you are reluctant to incorporate these tools into your own workflow (perhaps having cast them off quickly after some frustrated probing) and have a deep-seated skepticism of the tech that doesn't really matter what I say. 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.