They prefer it for a number of reasons, for better or worse. The big reasons I usually call out are: - packages should be buildable without calling out to any

They prefer it for a number of reasons, for better or worse. The big reasons I usually call out are: - packages should be buildable without calling out to any network resources. (this is the primary reason Debian dh-make-golang disables 1.11 style gomod support) - Debian specifically avoids vendored copies of code. This does create functionality and miantenance challenges, but it also produces a leaner installed code base. One again, for better or worse, this is a standing part of Debian package policy and warts from this particular choice stand out all over, not just golang. (newer Debian python, for example outright disables pip for non-venv python) There are other nits and warts that become apparent, but I think those all waterfall out from the two points I've called out here. (The Debian package policy in question: https://www.debian.org/doc/debian-policy/ch-source.html#embedded-code-copies https://www.debian.org/doc/debian-policy/ch-source.html#embe...)