My only issue with Go is getting the old bootstrap C version compiled for a new port... so it can build a modern release. In that area, the whole paradigm of needing only Go hits hard as a dependency reality check in some use-cases.
JavaScript frameworks just follow a well known trajectory... =3
Genuinely curious — how often have you had to do that? What platforms are you running that Node has binaries for but Go doesn't?
I've been writing Go for 12 years and it's never taken more than a couple minutes to download and install the latest version.
If you are porting Go, than you may find it has a legacy dependency on the deprecated version (rarely used except for the porting use-case) which is a problem on some platforms.
To list Node issues would be pointless, as most already re-discover them within minutes. =3