> You don't need a proxy to have git out of the loop for downloads or install time stuff. You do with go because go uses git tags for version information and m

> You don't need a proxy to have git out of the loop for downloads or install time stuff. You do with go because go uses git tags for version information and must parse the `go.mod` file at various versions. Go also supports git repositories hosted in places other than github, where there's no standardized way to fetch a single file at a tag (the go.sum file), or to perform a suitable search for a versoin and its metadata. > This [pulling github archives] is much faster than using Git That's only true if you only ever look at a single version of a library. If you have a 20MB git repo at v1.2.3, and ~100KB of files change for the v1.2.4 patch release, using the zip/tar archive means you have to download 40MB total to use it and update it to the new patch. Using the git repository in the first place means the update can only download 20MB since the new `fetch` will be effectively zero data, assuming you cache git stuff well.