tldr; YES ! You have to recognise the Go was spearheaded by folks who were there from the earliest days of Unix and Plan9 (used by IBM supercomputers). They k

tldr; YES ! You have to recognise the Go was spearheaded by folks who were there from the earliest days of Unix and Plan9 (used by IBM supercomputers). They know how not do do things. With all that experience you can accept that they have the experience to make good decisions. And those decisions are clearly documented and explained in the various documents. From a technical side, Go is statically linked. So can cross-compile and not have to face DLL nor shared library hells. Whilst the resulting binaries are larger than those that use shared libraries you can have many goroutines running at once. Each goroutine uses only a small amount of stack space. So for any production sized project the ease of deployment outweighs any incremental memory usage. After all, these days 32G or more memory is not unusual. On Google AppEngine - Go programs run faster and consume less resources than comparable programs written in Python and Java. Google is run by some very smart folks. They are unlikely to be going down a unviable path.