Re:Understanding the Go Compiler: The Linker
by vlinx on Saturday February 14, 2026 @08:19AM
(#47014325)
It's always fascinating to dive into the internals of the Go linker. One aspect I've found particularly clever is how it handles static linking by default, bundling everything into a single binary
[ Parent
| on HN ]
Re:Understanding the Go Compiler: The Linker
by MisterTea on Saturday February 14, 2026 @10:49AM
(#47015403)
The Go tooling is heavily based on the Inferno tool chain which was based off the highly portable Plan 9 tool chain. Plan 9 by default is statically linked as dynamic libraries are supported but not implemented anywhere. The idea was that librarys should instead be implemented as a service that runs local or on a remote machine.