Hacker News

nice, good to see more contributor in this space

It has to be 100% open source public code or we will have no way of proving this is not malware, or secretly swapped out for malware later when your CI/CD system or laptop is compromised. Supply chain attacks happen all the time and with closed code no one will be equipped to spot it when it happens.

Also, security aside, engineers want the freedom to modify and experiment with the tools we rely on.

Tools like this are too important to be closed. Do you want to be Internet Explorer or Firefox?

A GitHub repo with no source code is exactly equivalent to linking the binary directly

there are still many bad players in the industry, i wouldn't mind sharing it with trusted group. But I am not yet strong enough with deal and handle all those yet.

Just so everyone who reads this understands; despite the criticism in this comment, it's being incredibly charitable to LLMs in the context of making games. They're not particularly good at it and you wouldn't want most of the code they write in your game and especially not in the underpinnings of your game.

It's not true as a general rule that they could give you correct small code snippets five years ago; I had frontier models not even understanding enough of the OpenGL API to make separate framebuffers correctly. I asked this as a test and the resulting recommended code would of course compile, but leave someone who didn't already know the correct way to do it staring at a black screen and potentially spending the next hour debugging that.

If you think you're somehow going to make an actual game worthy of people's time with LLMs, you are almost certainly mistaken. Not only because it'll be a complete, unworkable mess with really bad fundamentals, but also because if you're vibecoding the actual technical part you probably also think game design is just about "having ideas" or something else that's really reductive and incorrect.

Seems visulization is still too expensive and sluggish. I tried to build things like tetris and snake eater with fable5 and got-5.6 sol, 90% of build successful in one shot and remaining needs 1~2 rounds debug. The whole experience is much better than months earlier, where a snake eater takes me 3~4 manually compile/run and input the error message and abnormal manually again and again.

But I am curious about building a larger scale game with/without professional engines like Godot. I highly doubt the model/agent is intelligent enough to setup the entire development environment correctly, thus may be struggle to test and debug themselves. Maybe something like GUI-agent a future?

Depends a lot on what model you use. Claude Sonnet/Opus, Deepseek, Mimo, M3 are smart enough to figure out how to create debug views, add single-frame screenshot and testing harnesses.

BTW, I also tried to make a entire LLM-driven bot to play boardgames like chess or mahjong, but it has the same latency issues since most of the online platforms have strict per-turn time limit like 15-30s, which is almost impossible for LLM/agent to react in time.

Sounds like every other plagiarist.

A classic tale from the music production world comes to mind:

"I thought using loops was cheating, so I programmed my own using samples. I then thought using samples was cheating, so I recorded real drums. I then thought that programming it was cheating, so I learned to play drums for real. I then thought using bought drums was cheating, so I learned to make my own. I then thought using premade skins was cheating, so I killed a goat and skinned it. I then thought that that was cheating too, so I grew my own goat from a baby goat. I also think that is cheating, but I’m not sure where to go from here. I haven’t made any music lately, what with the goat farming and all."

That's like saying you aren't building a house if you use a hammer to drive nails instead of your hand. AI is just a tool like any other, and you use it to build things like you would any other tool.

I know now we all are somehow like 'product manager' when using agent/chatbot, and we just need to setup requirements and point out issues. But in game area, I am not so sure models/agent are capable enough, especially involves heavy graphic related development and human interaction things? Since from my personal experience, even codex and claude code not so stable and efficient when dealing visualisation things like figures, videos and even much easier one - web-browser.

"A game" is a different abstraction layer from "a piece of software", though. A game has designed mechanics, a scenario (level design, etc.), art/music assets, writing, and so on. I would say that if you're making all of those things yourself, but you're having an AI write the software that executes the game, then you're still "building a game" per se. "Developing a game" even.

Compare/contrast: people who develop games on top of high-level genre-specific game engines like RPG Maker are still considered to be "building a game." What's the difference between using a pre-made purpose-fit engine like RPG Maker, vs. asking an AI (or, for that matter, a contracted software company) to build you a custom purpose-fit engine?

This is such a horrible cringe and bad faith take.

Eating food doesn't count if you didn't grow it yourself.

Same idea that sends people down needless game engine development / procrastination rabbit holes.

there is one toy version https://github.com/AntigmaLabs/nanochat-rs README updated.

the public repo README is updated.

will add those soon!

for now only some of core crates is migrated, will do so progressively

even with power of AI, we are mere human and still slow. Adding this to backlog.

yes. Offline mode is choice, should be able to run frontier one first and then figure out how do incorporate local models as real workhorse

Agreed! When a tool is explicitely marketed for offline use, opt-out telemetry feels especially contradictory. Should Definitely be opt-in by default...

Right? How hard is it to just ask a single opt-in question during installation. Opt-out just seems lazy, especially if I have to dig though configs to get to it.

feedback received, it was carry over from the preview dev build.