News for hackers. Stuff that matters.
Re:Go at Google: Language Design in the Service of Software ... by ChuckMcM on Wednesday December 05, 2012 @12:46AM (#4875080)
I wonder sometimes if Go will become to Google what TAL was to Tandem. A language uniquely suited to solve problems unique to the design space in which they operate. In Tandem's case it was non-stop computing, in Google's case its kilocluster distributed algorithms.

I really appreciate watching it evolve.

Re:Go at Google: Language Design in the Service of Software ... by burntsushi on Wednesday December 05, 2012 @03:45AM (#4875469)
I wrote a fully featured X window manager in pure Go [1] that I use full time. And it was pure joy compared to doing the same in C.

[1] - https://github.com/BurntSushi/wingo

Re:Go at Google: Language Design in the Service of Software ... by danieldk on Wednesday December 05, 2012 @03:25AM (#4875435)
Go is really too general for that to happen. From my (still limited) experience, Go is a safer C with garbage collection, interfaces and goroutines. What I like about Go is that the authors did not over-engineer the language and is pretty much as simple as C as a consequence.

Obviously, things like the garbage collector and bounds checking make Go slower than C. On the other hand, although the Go spec does not mention the stack or heap, you still have pretty much control over memory layout. E.g. making a slice of structs will be backed by an array of (unboxed) structs, pretty much as you'd expect.

Re:Go at Google: Language Design in the Service of Software ... by dualogy on Wednesday December 05, 2012 @01:34AM (#4875211)
Doesn't apply here, Go is largely as flexible, generic and versatile as C, minus a few restrictions and plus a few (awesome) additions. And the CGO interface lets you bind C libs as needed.

I write OpenGL apps in Go. Surely this is in no way characteristic of Google's internal use-cases.

Today's machines are multi-core and are not as bare-bones as to require manually carefully coded malloc/free calls. That's what's changed since C and that's what Go is (very well) designed for. Then a few syntactic goodies that don't imply performance side-effects or any black magic but that C didn't have: duck typing, struct composition, interfaces, all that.