Go produces static binaries, so it isn't really needed for production environments would be my guess. Devs tend to install upstream tools instead of the out of date RHEL tools too.
For instance -- Go has to link to glibc, and glibc doesn't provide proper support for static compilation (you _can_ do it but it's not actually supported in the RHEL sense by glibc upstream). And even when you force Go (through several magic incantations) to give you a static binary, networking and similar code will still use NSS (which uses dlsym and thus still requires dynamic libraries on the host to be installed).
and system administrators tend to install packaged tools instead of upstream tools that aren't tested to play well with the rest of the system.
Perhaps installing directly from upstream makes sense for Go, but the servers I maintain either run distro-packed software or custom software.
Too many bad experiences with upstream packages to trust on production.