In the midst of GitHub's outages and decline, many prominent people, such as Hashimoto are moving off of GitHub. Codeberg is one of the alternatives, and I've realized that we might want to make a CLI for AI agents similar to the purpose that `gh` has served for GitHub

So Pokemon Go but better

Pretty much Pokemon Go, but the Pokemon are replaced by your local churches and local castles with all the lore that comes with it :)

Didn't they write a whole blog post on why they chose Zig over Rust?

What about Gitea?

Forgejo is just the one I landed on, but like I said - there are options!

how do subagents work?

slightly unrelated but what’s with storing the entire codebase in the root directory instead of a nested src folder? It makes getting to the README a lot more difficult

Thats the default for go projects. Go imports are repository strings (e.g.):

     import ("github.com/go-sql-driver/mysql")

so it's standard to have the library files in the root directory.

FWIW I usually don't structure my Go projects this way unless they're very very small. This is what I usually do for anything larger than 2-3 files:

  ├── cmd
  │   └── binary-name
  │       └── main.go (may subpackage for things like CLI porcelain, etc)
  ├── go.mod
  └── internal
      └── app.go (and subpackages, etc)

I assume this is why GitHub has the annoying #readme-ov-file slug

I don't like go as a personal preference but reducing them to "fanboys" is a bit reductive. I'm sure the same could be said about your own favorite language.

Also as far as being civil: please watch literally any Rob Pike vibe chastizing Python and Java communities to no end. It is that rhetoric. That is why Go has fanbois. They can only see what the Gopher says and what Rob Pike says. Nothing else.

Other languages have fanbois but they didn't disparage and denigrate other communities to prove themselves.

Is it reductive when its describing a group of people that like something and refusing to hear any ill of it? The comment wasn't shade at people using the language in general.

And you're right, fanboys are in every language. But resorting to changing the argument by whataboutism is a bit reductive.

I’m not a go fanboy, but I do know from other contexts that so-called “fanboy“ behaviour is frequently associated with level-headed supporters getting defensive in the face of imprecise criticism.

There’s an oft-repeated pattern where valid specific criticisms morph into broad criticism, which morphs into judgement, which breeds defensiveness, which feeds the criticism. Once you recognise this pattern, you see it everywhere.

Thats the defensive step outlined above.

I believe it was "They were all like who needs generics in go. and now go has go generate and templates."

I guess I qualify as a Go fanboi -- it is not perfect but gets the job done for a lot of us, sorry it doesn't work for you.

But back to your point about "vomit in the root dir", Go does have namespacing of sorts via packages, and the pattern you criticized is not the only way -- often just a simple main.go at the root bringing in packaged functionality.

Ok... The question was why is it like that. The answer is because it's in go. Nobody was anything other than civil before you neckbearded in here. Chill. There's a sane way to say what you said.

I wish I could grow a beard. Also as far as being civil: please watch literally any Rob Pike vibe chastizing Python and Java communities to no end. It is that rhetoric. That is why Go has fanbois. They can only see what the Gopher says and what Rob Pike says. Nothing else.

Note that Rust is not in fact named after Fe2O3; it’s named after a resilient fungus of the same name

Just goes to show how little I know about Rust.

is there a CLI?

You have to try Codex. My friend's been trying to convert me for months and he was right all along: with Codex you don't GSD or whatever prompting metaframework. You rarely (I actually haven't need to do this at all) need to ask it to retry because its implementation is bugged: it literally just works first try.

Maybe that's because the harness maybe (not sure; haven't looked at their source code) has it baked in? Doesn't matter; the point is that it works.

Now, the one thing I heavily dislike is the UI it generates...it doesn't seem to realize that matching UI patterns with the existing codebase is quite important.

TY!!

Yea this actually has been going viral when I posted it on Instagram. Maybe I'll need to post this on HN in a different time or wait for someone else to organically post it :)