[daitangio]

Go static linking is a great happy idea for a Java guy trapped in the Classpath Dependency Hell (or C# / DLL Hell).

It is a very annoying thing for a C++ programmer, which can dynamically link operating system libraries at will.

[kstenerud]

"DLL Hell" was coined in the early days of Windows (before C#), and originally referred to C and C++ dynamic library problems.

[skrebbel]

You mean a C++ programmer who does not care whether their program works on anybody else's computer?

[synergy20]

in that case you can happily static-link c++ programs, which probably will be smaller than go binary.

[anthk]

happily and "statically link c++" don't match together well.

[pjmlp]

They do, there are more C++ compilers out there than gcc with glibc.

[anthk]

Go's static linking idea comes from plan9 C compilers, a few years before Java. We owe a lot from plan9:

- Go's design, based on both C compilers and Inferno's limbo

- /proc

- utf-8

- 9p

[eklitzke]

/proc does not come from plan9: http://dtrace.org/blogs/eschrock/2004/06/25/a-brief-history-...

[anthk]

Unix 8/10 -> Plan9 :).

Rio's foundations come from the Blit.

Unix 8/10 was not a big success, but a lot of ideas from that went into Plan9.