It's also probably worth noting that 'go get' isn't really a package manager in 
the way that yarn and npm are. Each of those tools, and their go equivalents 
[1] have somewhat more sophisticated functionality related actually managing 
the packages, controlling their versions, resolving conflicts, etc. while 'go 
get' basically retrieves a package and it's dependencies if they aren't already 
present. If you're working on anything that needs to be relied upon, it's 
probably worth checking out Go's package manager ecosystem. For what it's 
worth, we use glide where I work and it has lots of output :)


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 
For more options, visit

Reply via email to