News for hackers. Stuff that matters.
Re:How We Went from 30 Servers to 2: Go by jbooth on Tuesday March 12, 2013 @10:44PM (#5366480)
They're not similar at all, but both were designed to replace C++. That sort of means that they're competing for the use-case of "things I would write in C++ if it wasn't a god-awful nightmare to do so".

From there, though, you're right that they take very, very different approaches.

Re:How We Went from 30 Servers to 2: Go by azakai on Tuesday March 12, 2013 @11:34PM (#5366650)
> They're not similar at all, but both were designed to replace C++.

In practice, the main use for Go appears to be like this story - an alternative to RoR, Node, Python/Django, etc. - and not a C++ alternative. Go and Rust may both start from the idea of doing C++ or something similar "right", but end up in very different places.

Re:How We Went from 30 Servers to 2: Go by coldtea on Wednesday March 13, 2013 @05:31AM (#5367553)
>They're not similar at all, but both were designed to replace C++.

Well, Rust WAS designed to replace C++, both in the intention behind its design and the way it was done.

Go designers had this vague intention of "replacing C++", but the way they have designed the language they only really replace Java or some scripting language. Which they admit (the get mostly Python etc converts than C/C++ converts).