[tomwilde]

You are right yet Go is much closer to C than Erlang in syntax, type system and memory-representation. Go is so close to C in fact, that its compiler is a modified C compiler.

Therefore I'd bundle it with C and D rather than Erlang.

[voidlogic]

I think of Go as "C++", but as brought to you by the guys who made C, with tasty sprinkles from CSP and Python.

[coldtea]

It's mostly Java from the people who made C, but didn't learn much from their C design mistakes.

[voidlogic]

Ridiculous. Go's lack of verbose classes and lack of inheritance, pass everything by value, the existence of pointers, first class concurrency primitives, compile to binary / no interpretation/JIT, lack of a VM, built in unit testing/benching, fast compile times, memory usage, easy C integration, etc etc all make it very different from Java.

I've been writing Go full-time for over 2 years and used to write mostly Java/C#, so I should know. When I started with Go and ported many of my personal Java applications, they all were much more maintainable and straight forward in Go.

Of course C had always been favorite language, and all I ever really wanted was a "modern" C, so I am probably biased.

[agumonkey]

Agreed, I meant Erlang for its use. It's hard to be more different than Erlang in implementation :)