News for hackers. Stuff that matters.
Re:Golang at CloudFlare by pjmlp on Tuesday July 03, 2012 @04:31PM (#4196045)
The only reason this is not an issue with Go is that the language is too young and the reference compiler only supports static linking fot the time being.

The moment the compiler starts supporting dynamic linking the same will happen to Go.

Re:Golang at CloudFlare by koenigdavidmj on Tuesday July 03, 2012 @04:55PM (#4196151)
The Plan 9 people (basically the same group as the Go people) have some philosophical problems with dynamic linking. Read http://harmful.cat-v.org/software/dynamic-linking/ for their arguments.
Re:Golang at CloudFlare by 4ad on Tuesday July 03, 2012 @04:54PM (#4196146)
Static linking of Go code is a conscious design decision, not some artifact of toolchain immaturity. It will never change.
Re:Golang at CloudFlare by pjmlp on Wednesday July 04, 2012 @01:26AM (#4197760)
You can make use of dynamic linking with gccgo, as far as I am aware.
Re:Golang at CloudFlare by reddit_clone on Tuesday July 03, 2012 @05:22PM (#4196251)
On a related note, using Go can one develop DLLs that can be dynamically consumed from other applications?

Or you can only produce statically linked exe's?

Re:Golang at CloudFlare by zimbatm on Tuesday July 03, 2012 @06:40PM (#4196581)
Only exes at the time being. Go is the main loop and needs to have control of the execution flow for concurrency.

If you think of it, DLLs are a bit like separate programs that you communicate with trough the C call stack instead of another structured protocol. In Go you would spawn different processes and use something like protobuf to exchange messages.