A few reasons off the top of my head... Go has very simple dependency management. A library written in Go generally needs very little environment management an

A few reasons off the top of my head... Go has very simple dependency management. A library written in Go generally needs very little environment management and will often integrate easily with a Go codebase. This is further enhanced with Go’s implicit inheritance model. Go compiles to a static linked binary. A library written in Go usually can be static linked as well with no system dependencies. Go has excellent cross platform support. Unless a library makes system calls (and sometimes even then), it will also be cross platform. Go has a clean, simple, style. The lack of features like generics, operator overloading, and constructors means you can look at the code and instantly understand what it does. There is no spooky action at a distance because a variable declaration turns out to be a complex function call. This makes it much easier to understand the overall system impact of using libraries written in Go. Applications and libraries written in Go build very quickly. My experience with other languages is that trying a substantial new package is a go-make-a-sandwich level of inconvenience. Go libraries usually are ready to use as soon as git clone finishes.