Currently, go get produces no output on a successful install. This can lead to confusion for new programmers, as it is not clear that the command is doing anything, especially if you are used to the like of apt, which will give you a massive wall of text whenever you download something. This is made worse if you are downloading a large package, as it might look like the program has frozen.
I'm not sure if this should be the default behavior or not, as changing the default command output could break scripts. Making it a flag would solve this, but could reduce benefit for new devs.
definitely not default, and there is -v for more verbose output/progress
Please no. Let the command continue to run quietly if there's nothing to report.
As Rob said, most go commands are quiet by default, and this is unlikely to change. See #22800, #22356, #17959, #18388; in particular https://github.com/golang/go/issues/18388#issuecomment-268315634.
Closing this discussion as a dup of the above.
I looked through the issues, and one thing noone seemed to mention is that -v still doesn't output that much. I think an easy compromise would be a flag to pipe the output of sub-commands (e.g. git clone) to stdout. maybe something like -vv?
Most helpful comment
Please no. Let the command continue to run quietly if there's nothing to report.