So fun fact: if you use CGO, your binary effectively ends up with two versions of libc. It statically compiles musl into the binary itself for Go code and it dy

So fun fact: if you use CGO, your binary effectively ends up with two versions of libc. It statically compiles musl into the binary itself for Go code and it dynamically links in libc for any C code. I'm not sure why there isn't an option with CGO to skip statically linking musl. You're depending on the platform libc regardless and at least then you end up with a smaller binary.