Because that's good practice for a cli-tool. No output means success. Only print information that is actually needed. For a successful go-get, that's none.
On Thu, Oct 13, 2016 at 11:48 PM, Nyah Check <check.n...@gmail.com> wrote: > Hi everyone, > > I don't know if someone may have talked of this here. But I just wish to > find out why `go get` is entirely quiet by default? Unlike other package > managers like npm or yarn. Someone asked this on the IRC channel today and > no one seemed to know why? I tweeted > <https://twitter.com/nyah_check/status/786547656155725824> about this > today; still no response yet. > > Thanks, > Nyah > > "The heaviest penalty for declining to rule is to be ruled by someone > inferior to yourself." --*Plato* > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
