[maybewhenthesun]

Maintainer nightmare checklist:

- Web framework : inherently hard to maintain due to communication over evolving standards. Check.

- AI written code where nobody knows howwhatwhenwhy!? Check.

- Written in C. Check.

bwahahahaha!

edit: semi-joking. As I actually like the simplicity of pure C. But the combination of AI written,network-facing and C makes me shudder.

[ashtonjamesd]

Haha, I have used AI in some parts of it - mainly the JSON part because I could not wrap my head around it for the life of me. But I am proud that 90% is self written!

[le-mark]

In that case the json parse function might be a bit of a challenge. It should actually be pretty straight forward with the builder functionality you’ve got in there. Loop over the input and use a state machine (switch block with a state variable) keep track of what you’re doing. Oh and you’ll need to recurse or otherwise use a stack to keep the nesting levels correct. Ie objects that contain arrays or objects, arrays that contain arrays, etc.

[isubkhankulov]

I can see this becoming a trend. People putting badges on their repo as to how artisanal, organic and “authentic” their code is.

[jvanderbot]

That is excellent. Well done.

[jvanderbot]

I think the old HN ethos that I loved, on full display here, won't survive intact in the AI era. It'll have to change from "It is cool to try making <neat tool> in <non obvious language>". Such a project is now a prompt away, and there's light-years of distance between a carefully hand crafted version and something that is posted aspirationally by an AI.

Every agent I know of or use will always say they built "Production ready, secure, fast package for X" if you ask them to build that, but they rarely actually will. It takes enormous time and effort to actually do that, and any first iteration of "production ready" is definitely aspirational until it actually hits the real world and survives. I'm speaking from experience, fwiw.