Hacker Newsnew | past | comments | ask | show | jobs | submit | verdverm's commentslogin

The have Rust now so the entire tooling layer can justifiably be rewritten a few more times

If everyone put "open" in their project's name because it was open source, almost all the software we use would have "open" in the name

The open source / open plugins / text files is not unique to your project. The majority of the ai tooling space is open in the same way


I'm imagining an ADK swipe skill

I've gone so far as to become frustrated with what I found in the open source options like Copilot and have been building my own custom extension, which is now better with gemini-3-flash than Copilot is with any model. Their prompt/context engineering is trash and their tools are not great

Very cool, always love seeing adventures in codegen. If you want to see what something like this looks like after many years of development, after you discover all those day-2 issues in code gen at scale...

intro code gen docs: https://hofstadter.io/getting-started/code-generation/

core code gen package: https://github.com/hofstadter-io/hof/tree/_next/lib/gen

you'll likely want to move from printf to text/template and then put a schema on the input data, then put the templates as files on disk so you can iterate faster without needing to recompile the binary to adjust the code that comes out

btw, you contributed the built binary to your git repo


Is the plan to contribute them back to Go?

How is a one person fork of Go in any way going to ever be more secure than the original which is developed by many people? Why should I trust your changes? Is this actually an adversarial project that will hide and rug pull down the road?


1. "Is the plan to contribute them back to Go?" - No. They won't accept the up-streams. See https://github.com/golang/go/issues/30613

2. "How is a one person fork of Go in any way going to ever be more secure than the original which is developed by many people? " - Read the README.

3. "Why should I trust your changes?" - You don't have to. The same reasons you don't have to trust the Github project you're cloning.

4. "Is this actually an adversarial project that will hide and rug pull down the road?" - Read the code.

Sarcasm aside, the objective is "helping to find bugs in Go codebases via built-in security implementations". That's mainly used for fuzzing and testing. Don't deploy you compiled binary on production with that compiler.


If the Go team will not accept your changes, I would trust their judgement over yours 100%

Do you mean Windsurf? Google did not write Antigravity, they paid $2B to whitelabel someone else's product

Like this? (Obfuscated, from agent and history)

https://bsky.app/profile/verdverm.com/post/3mbo7ko5ek22n


Yes, I'm using Dagger and it has great secret support, obfuscating them even if the agent, for example, cats the contents of a key file, it will never be able to read or print the secret value itself

tl;Dr there are a lot of ways to keep secret contents away from your agent, some without actually having to keep them "physically" separate



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: