Hacker News new | ask | show | jobs
by BearOso 81 days ago
You have to maintain a completely separate implementation of AI generated code that's translated from C, so not even idiomatic zig.

Edit And then I go their repository and read commits like this https://github.com/hdresearch/ziggit/commit/31adc1da1693e402... which confirms it wasn't even looked over by a human.

2 comments

I don't know zig well. What's raising flags for you?
The commit I linked shows that it didn't even read the user name and email from git's config file, but used a test name, which means it's woefully incomplete.

Then there's stuff like this: https://github.com/hdresearch/ziggit/blob/master/src/cmd_bra...

It's just one giant function. Sometimes big functions are necessary. This one is clearly AI generated and not very readable for a human. This is just from a quick glance.

This was orchestrated and developed by agents with verifications like the codebase compiling or git's CLI test suite passing.

That was so the commit authors don't all appear like blank accounts on GitHub

Surely "the commits are attributed to the user who creates them" is a pretty basic feature of the git CLI, and not something that you can add in as a fix later after posting your project to Github and writing a blog post about how much faster than git it is.

It's very easy to be faster than git's CLI if you don't have to do any of the things that git's CLI does!