1. I&#x27;m not certain on the precise binary layouts etc, but I believe the answer is &quot;yes, except Go binaries can&#x27;t be stripped&quot;. In terms of practical usage, they&#x27;ll run on the same machines.<p>2. This is a long one.<p>The statement you&#x27;ve quoted is false. However, it&#x27;s both a) a common misunderstanding and b) a sort-of-ok simplification (the full story is much more involved). I&#x27;d personally alter it to say &quot;it is technically challenging to statically link glibc&quot;. You can read more about the whole musl Rust origin story at [0]. The &#x27;problem&#x27; with glibc is that it uses NSS, a feature that allows you to dynamically load libraries installed on the system to let you change how some libc functions work (if neither you nor your libraries use these functions, static linking with glibc works). For example, musl will look up users from &#x2F;etc&#x2F;password, whereas with glibc an admin can install an LDAP library, change a config file and all programs using glibc will magically use LDAP. But, you can disable NSS in glibc at compile time [1], which <i>then</i> allows you to truly statically compile with glibc.<p>Go is interesting because doesn&#x27;t use libc at all (when using the standard compiler)...<i>except</i> when doing some network things that NSS is useful for, when it does link against it. People who want totally static binaries pass a few additional flags to say &quot;don&#x27;t use NSS, use the Go implementation of these features&quot;...and you then end up with bugs like [2].<p>3. Yes [3], but you lose (by default) a) the ability to use shared libraries from the system, b) NSS. Given that one angle Rust is pushed from is &quot;C&#x2F;C++ replacement&quot;, not being able to link to system libraries without using arguably cryptic command line arguments would be a bit sad. But I&#x27;m ambivalent about this.<p>[0] <a href="https:&#x2F;&#x2F;internals.rust-lang.org&#x2F;t&#x2F;static-binary-support-in-rust&#x2F;2011" rel="nofollow">https:&#x2F;&#x2F;internals.rust-lang.org&#x2F;t&#x2F;static-binary-support-in-r...</a><p>[1] <a href="https:&#x2F;&#x2F;sourceware.org&#x2F;glibc&#x2F;wiki&#x2F;FAQ#Even_statically_linked_programs_need_some_shared_libraries_which_is_not_acceptable_for_me.__What_can_I_do.3F" rel="nofollow">https:&#x2F;&#x2F;sourceware.org&#x2F;glibc&#x2F;wiki&#x2F;FAQ#Even_statically_linked...</a><p>[2] <a href="https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker&#x2F;issues&#x2F;1715" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker&#x2F;issues&#x2F;1715</a><p>[3] (specific post from [0]) <a href="https:&#x2F;&#x2F;internals.rust-lang.org&#x2F;t&#x2F;static-binary-support-in-rust&#x2F;2011&#x2F;17" rel="nofollow">https:&#x2F;&#x2F;internals.rust-lang.org&#x2F;t&#x2F;static-binary-support-in-r...</a>