Go 1.5 Released, Its Compiler Toolchain Is Now In Go

[phoronix]

Phoronix: Go 1.5 Released, Its Compiler Toolchain Is Now In Go

Go 1.5 has been officially released!..

http://www.phoronix.com/scan.php?page=news_item&px=Go-1.5-Released

[wargames]

Go away Go go go

[Daktyl198]

As somebody who's never really touched Go... does the person running the program have to have Golang runtime libraries installed? Or do they get packaged when you compile the program?
I'm assuming this because it uses a GC and other runtime features that are more advanced than, say, a C runtime which is fairly minimal in comparison (and doesn't really affect the size of your programs).

Just wondering.

[veeableful]

As somebody who's never really touched Go... does the person running the program have to have Golang runtime libraries installed? Or do they get packaged when you compile the program?
I'm assuming this because it uses a GC and other runtime features that are more advanced than, say, a C runtime which is fairly minimal in comparison (and doesn't really affect the size of your programs).

Just wondering.

It's statically linked by default so a simple hello world program would be around 1MB with most of the stuff being the runtime. There is an option to compile packages as shared libraries but kinda pointless for most use-cases.

[Daktyl198]

It's statically linked by default so a simple hello world program would be around 1MB with most of the stuff being the runtime. There is an option to compile packages as shared libraries but kinda pointless for most use-cases.

Thanks

[DrYak]

Now that the Go toolchain is written in Go, how are you even supposed to bootstrap it ?

I mean with GCC it's easy: it's written in C, and there are C compilers written for almost anything able to running code under the sun.
You're bound to find some C compiler in which to build a preliminary bootstrap of GCC.

But with Go ? Go compilers aren't as ubiquitous as C.

[veeableful]

Now that the Go toolchain is written in Go, how are you even supposed to bootstrap it ?

I mean with GCC it's easy: it's written in C, and there are C compilers written for almost anything able to running code under the sun.
You're bound to find some C compiler in which to build a preliminary bootstrap of GCC.

But with Go ? Go compilers aren't as ubiquitous as C.

You just download the Go binary and use it to bootstrap Go. The binary is statically-linked so you can run it pretty much anywhere without worrying about missing some dependencies.