linking

If you mean the one that comes with the OS, then wouldn't that by dynamic linking?

Great to see someone else linking to bravenewclimate.com - this is a sorely under-read and under-linked resource.

Static linking isn't as easy for other language platforms, as some issues crop up (a google/SO search shows many questions).

It's hard to be sure why exactly shared libraries and dynamic linking appeared.

Is it a good idea to start linking content in other languages?

Dynamic linking is the number one binary compatibility issue on Linux.

What Go makes different still is that static linking is mandatory.

But if the facts are otherwise, then I hope I've done a good job of linking to and explaining public information.

Often it is as simple as not having the static libraries available, or having difficulty linking with them because they still want to dynamically load other libraries.

The original authors of dynamic linking concluded that the cost was way higher than the benefits, both in memory usage and general performance, but the client demanded it.

Go 1.5 has mechanisms for dynamic linking, though.

But that's my point: we should be able to get automatic linking.

Linking several hundred objects in a dozen or so libaries out of 2.5kish objects together is going to get hairily expensive memory wise no matter what way you do it.