👋 so I'm just learning about zenith/

[teal mantle]

as a corrolary to this, I saw vikram merged a go module getting started guide to the docs. Is there in general just a high level overview for people before they start implementing and using modules? I'm interested in playing around with zenith now that it's come pretty far along and am looking for a place that I can just start from and get a hello world going

[hollow wing]

I think this is the page you're looking for: https://docs.dagger.io/zenith/developer

how are modules glued together under the hood?

At a high level, each module executes in a container and the interface between modules is graphql, the same way the SDKs interact with the engine today. The main difference is that now you can extend the core dagger API with more modules

How do you envision bootstrapping a new developer?

The flow you mentioned is still totally valid (although isn't supported quite yet for zenith). But in a pure module world, you can git clone, install the dagger cli, and then run dagger functions to see what functions are available and how to use them. It might list build as an option, and you could run dagger call build --help to see more information. All without having to build your own CLI.

One upside to this compared to the previous world is that they don't need Go. This is great because that also means the version of Go they may or may not have does not come into play. It also means that you no longer care what language the CI tooling is written in

[halcyon tapir]

That's pretty cool, and I glossed over the fact that I'm confident new devs will have an old version of golang installed. 😉

I think dagger call test is gonna be better than make test even if it's more to type, but I feel pretty strongly that devs need the toolchain natively* on their system for day-to-day development.

*not containerized

[hollow wing]

Yeah exactly, in that case you can replace make with dagger, but forget about all of the dev dependencies

*except a container runtime 😉