News for hackers. Stuff that matters.
Re:Golang at CloudFlare by riobard on Tuesday July 03, 2012 @02:04PM (#4195308)
Another reason Go has been helpful is that is generates a single executable that can be distributed to our clients. There's no complex dependency chain or layout of shared libraries to worry about.

This is such a subtle yet profound feature. Think about it: no more dependency nightmare during deployment!

Re:Golang at CloudFlare by Strom on Tuesday July 03, 2012 @02:27PM (#4195453)
Static linking is easily available with C/C++ as well. The main trade-off is how critical bugs in some library your program uses can be solved.

With dynamic linking it's possible for the library author to publish an API-compatible update, which when deployed fixes the issue in all programs that use this library. With static linking you need to recompile the whole program and publish the update.

For real world examples you could look at the Microsoft C run-time. When a security vulnerability is found & fixed, Microsoft pushes the dynamic link version of the update via Microsoft Update and millions of programs are no longer affected by this issue. However when you linked statically, you need to update your program as well. Many programs do not have good automatic update systems, and many programs aren't even under continued maintenance and remain forever vulnerable.

Re:Golang at CloudFlare by Splines on Tuesday July 03, 2012 @04:15PM (#4195971)
I wonder if there's a way to have your cake and eat it too.

Publish your app as a dynamically linked binary to an app publisher, the publisher takes your dll and mashes it with its dependencies into a single dll that they deliver to the customer.

When there is a security update in a dependent dll, a new binary can be delivered by the publisher to the customer with no need for the original author to push a button.

I'm guessing something like this exists already?

Re:Golang at CloudFlare by jkn on Tuesday July 03, 2012 @03:43PM (#4195825)
Static linking is not easily available with C/C++ in the general case. Some libraries support it, some important ones like Glibc and GTK+ do not.
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.

Re:Golang at CloudFlare by 1amzave on Tuesday July 03, 2012 @06:38PM (#4196577)
Huh? Perhaps you mean Glib? Static linking works just fine with glibc:

  [me@host: tmp]% cat > hello.c
  #include <stdio.h>
  int main(void) { printf("hello world\n"); return 0; }
  [me@host: tmp]% gcc -o hello -Wall hello.c -static
  [me@host: tmp]% file hello
  hello: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 2.6.32, not stripped
  [me@host: tmp]% ldd hello
  	not a dynamic executable
  [me@host: tmp]% ./hello 
  hello world
Re:Golang at CloudFlare by saurik on Tuesday July 03, 2012 @06:44PM (#4196598)
I largely agree with you, but for what it's worth, that doesn't "just work": there are places in glibc that use dlopen to pull in modular code; one example is the DNS resolver.
Re:Golang at CloudFlare by tedunangst on Tuesday July 03, 2012 @08:34PM (#4197000)
As mentioned, if you try that it works less than 100%. Trying to run a 32-bit program on a 64-bit host will fail in weird ways unless some of the expected bonus libraries are available.
Re:Golang at CloudFlare by gillianseed on Tuesday July 03, 2012 @07:29PM (#4196807)
Although I've never tried it myself I've read that gtk supports static linking, iirc you have to build gtk with --disable-modules.

Also, Go has gtk bindings, how does that work?

Re:Golang at CloudFlare by jkn on Wednesday July 04, 2012 @02:05AM (#4197864)
Ah you're right, it seems you can get a static build by recompiling GTK+ and its dependencies with the appropriate flags and some extra manipulation... See http://wiki.inkscape.org/wiki/index.php/CompilingStatic for an outdated example. I don't know if that would work on Windows, it used to be not supported: http://readlist.com/lists/lists.sourceforge.net/mingw-users/...
Re:Golang at CloudFlare by tedunangst on Tuesday July 03, 2012 @08:31PM (#4196990)
Go can dynanmically load C libraries I believe, but there is no support for native shared go code.
Re:Golang at CloudFlare by 4ad on Wednesday July 04, 2012 @07:44AM (#4198957)
That is correct.
Re:Golang at CloudFlare by johnm on Tuesday July 03, 2012 @05:00PM (#4196165)
Makes the choice of using them that much easier. :-)
Re:Golang at CloudFlare by georgemcbay on Tuesday July 03, 2012 @04:44PM (#4196101)
This also makes cross-compiling a breeze. I write software in Go for armv5 chumby devices but I edit and compile on Windows (the Go compiler itself can be compiled and run on the chumby devices, but they are very slow and low memory for doing active development on).

Getting a build for the chumby from my Windows/x64 box is as easy as setting GOARCH=arm, GOARM=5 and GOOS=linux and then re-running go build. Ridiculously simpler than setting up a full gcc toolchain that targets the device, taking into account what libc is on each device, etc. Build on the Windows box, scp the output executable over and It Just Works.

Re:Golang at CloudFlare by riobard on Tuesday July 03, 2012 @08:24PM (#4196974)
Ha, this is very cool. I didn't know you can cross-compile Go before. Just tried and it's really easy to setup a build for multiple architecture. Thanks for the tip!
Re:Golang at CloudFlare by Dobbs on Tuesday July 03, 2012 @02:24PM (#4195437)
This is one of my major annoyances with python and ruby. I want to take all the package dependencies and toss them into a single executable that at most relies upon the interpreter to be there.

With a bit of hacking you can do it but it isn't the most straightforward procedure, can be messy and isn't really supported by the community.

Re:Golang at CloudFlare by gecko on Tuesday July 03, 2012 @04:34PM (#4196049)
The Python side's actually really easy and well-supported: Python can run code from a zipfile, so tools like `py2exe` or `pyinstaller` get you down to Python interpreter + zipfile. That's two files, but only two files. I don't know if there's similar stuff on the Ruby side.
Re:Golang at CloudFlare by wahnfrieden on Tuesday July 03, 2012 @04:37PM (#4196067)
It gets much messier once you have dependencies that aren't pure python. Last I checked py2exe was no longer maintained either.
Re:Golang at CloudFlare by davidw on Tuesday July 03, 2012 @06:05PM (#4196447)
Tcl has really good support for this, actually. It's a bit of a messy concept, but in the end, it works out pretty well.
Re:Golang at CloudFlare by TazeTSchnitzel on Tuesday July 03, 2012 @02:18PM (#4195395)
You can do the same thing with any compiled language, but I suppose that's a feature of Go since it's a compiled language.
Re:Golang at CloudFlare by genbattle on Tuesday July 03, 2012 @06:20PM (#4196504)
With other languages such as C/C++ if you link a library into your program statically, that library may dynamically load other dependencies. In Go, all dependencies have to be statically compiled into that package.

Rob Pike made a good point about this in one of the Go talks [1] (I think it was the "Meet the Go team" talk) when they were talking about package management and the static linking, and how in C++ you could get massive chains of useless includes (I think is came out of a question on the speed of the Go compiler). His reasoning was that all the code you need to compile a package should be in the one package binary. You shouldn't need to worry about having other 3rd-party packages that your dependency depends on installed on the target system.

[1] http://blog.golang.org/2012/07/go-videos-from-google-io-2012...

Re:Golang at CloudFlare by pjmlp on Wednesday July 04, 2012 @01:33AM (#4197777)
> In Go, all dependencies have to be statically compiled into that package.

This is not true. If you make use of cgo, the dependencies are linked dynamically.

Re:Golang at CloudFlare by 4ad on Wednesday July 04, 2012 @07:52AM (#4198986)
Using cgo is an exception rather than the rule, and when Rob talks about package dependencies he means any file required for building that package, not only the shared objects. This includes C/C++ header files. Even with cgo, to use a package that uses cgo you only need that package archive, you need not care about what files that created that package.
Re:Golang at CloudFlare by pjmlp on Wednesday July 04, 2012 @09:48AM (#4199389)
Like in every other compiled language that has modules.
Re:Golang at CloudFlare by genbattle on Wednesday July 04, 2012 @04:49PM (#4200806)
Yes, you are right. I was referring to pure Go packages.
Re:Golang at CloudFlare by riobard on Tuesday July 03, 2012 @02:27PM (#4195451)
You can do the same thing with any compiled language

This is not necessarily true. Remember the DLL hell? Go does not support dynamic linking at all (some say this is a disadvantage), so you are forced to produce a single self-contained binary.

Re:Golang at CloudFlare by TazeTSchnitzel on Tuesday July 03, 2012 @02:30PM (#4195469)
DLL hell only happens if you use dynamic linking. Static linking is always an option. (actually, is it? I don't tend to use a lot of libraries, how much stuff that isn't part of the OS can you not statically link?)
Re:Golang at CloudFlare by podperson on Tuesday July 03, 2012 @02:37PM (#4195503)
DLL hell happened (in Windows) because you had to dynamically link against system libraries which could change in incompatible ways making your code fragile.

Depending on the nature of the development toolset, you may not be able to avoid DLL hell. E.g. you may not have the right to build the library into your code and/or the toolset may force you to link against external code libraries.

The original goal of Microsoft's DLL strategy was to save disk space (and presumably memory) but the end result was a compatibility nightmare. Retrospectively, it seems to have been both a bad technical decision (disk space turned out to be a bad thing to trade against other considerations) and badly implemented (too many DLLs went live and then broke backwards compatibility in updates). It seems like other companies managed to allow dynamic linking without creating so much fragility.

Re:Golang at CloudFlare by gouranga on Tuesday July 03, 2012 @03:30PM (#4195771)
It's a great idea and still is. Linux does pretty much the same thing.

It actually broke because they didn't allow multiple versions and windows linked to the latest version at runtime.

They fixed all this with WinSXS which allows a PE file to specify a manifest i.e. a list of required versions of DLLs to load. This is all neatly explained here:

http://msdn.microsoft.com/en-us/library/aa376307.aspx

Re:Golang at CloudFlare by tedunangst on Tuesday July 03, 2012 @08:38PM (#4197011)
It would be more accurate to say dll hell happened because vendors decided to install their 3rd party dependencies in the windows directory. There are not as many problems with actual Microsoft dlls.
Re:Golang at CloudFlare by 4ad on Tuesday July 03, 2012 @03:59PM (#4195891)
> Static linking is always an option.

Not if you use C and glibc (most common combination of them all, most software requires glibc). Even if you compile glibc statically in your program (not an option by default at least in Ubuntu), glibc itself will load more shared objects at runtime.

Re:Golang at CloudFlare by yorhel on Tuesday July 03, 2012 @04:09PM (#4195938)
I've had very positive experiences with statically linking against musl[1], As long as your code and the required libraries don't use dlopen() tricks (e.g. as glib GIO does), you can quite reliably create a single statically linked binary for your program. Admittedly, this isn't as easy to setup as Go is.

[1] http://www.etalabs.net/musl/

Re:Golang at CloudFlare by tedunangst on Tuesday July 03, 2012 @08:41PM (#4197019)
You can statically link if you also compile a static glibc with modules disabled. But it's a pita and you can still have kernel compat problems.
Re:Golang at CloudFlare by TazeTSchnitzel on Tuesday July 03, 2012 @04:07PM (#4195932)
Oh, huh, I didn't know about that.
Re:Golang at CloudFlare by Strom on Tuesday July 03, 2012 @02:36PM (#4195499)
I belive you need to also provide re-linking mechanisms for your customers if you statically link something licensed under LGPL.
Re:Golang at CloudFlare by sausagefeet on Tuesday July 03, 2012 @03:08PM (#4195665)
Definitely. One reason I like Ocaml so much.
Re:Golang at CloudFlare by drivebyacct2 on Tuesday July 03, 2012 @02:55PM (#4195589)
The other nicety that goes hand in hand with this is crazy simple cross compiling. My current project uses cgo and pcap so I don't get to use it now [1], but my last and next project allow me to hit a single command and have nice statically compiled binaries for FreeBSD, OS X, Linux and Windows in a very small amount of time with almost no setup effort.

I still need to get it wired up to the GitHub API for downloads and life will be perfect. I can push to master and upload a build for download all in one fell swoop.

([1], cross compiling is not [currently?] supported with cgo)