News for hackers. Stuff that matters.
Re:How We Went from 30 Servers to 2: Go by azakai on Tuesday March 12, 2013 @07:16PM (#5365659)
Rust and Go are not similar or competing. They are both new, but aside from that the differences are huge. So if a project uses one, that doesn't mean the other was a possibility for that project too.
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).

Re:How We Went from 30 Servers to 2: Go by steveklabnik on Tuesday March 12, 2013 @07:29PM (#5365727)
The Rust team agrees: https://github.com/mozilla/rust/wiki/Doc-language-FAQ (control-f for 'this Google language')
Re:How We Went from 30 Servers to 2: Go by DASD on Tuesday March 12, 2013 @07:21PM (#5365689)
Indeed they are not similar but wildly different tools are often used in a similar or competing use cases(eg. the blog's post of the company using Ruby and conversion to Go). I had asked because if you were to reverse the usage do you think Google is likely using much Rust since it is developing Go?

Just to clarify, I see a bright future for both languages.

Re:How We Went from 30 Servers to 2: Go by tmzt on Tuesday March 12, 2013 @09:35PM (#5366241)
It would be interesting to see Rust used in Android in some of the parts that are now C or C++.
Re:How We Went from 30 Servers to 2: Go by Symmetry on Wednesday March 13, 2013 @11:08AM (#5368957)
The way I would put it is that Go was designed to incorporate some of the simplicity and speed of C as well as the ease of use of Python, while Rust was designed to combine the speed and flexibility of C++ with the safety of Haskell.
Re:How We Went from 30 Servers to 2: Go by steveklabnik on Wednesday March 13, 2013 @05:28PM (#5371229)
... and the concurrency of Erlang. (and OCaml might be more apt than Haskell).
Re:How We Went from 30 Servers to 2: Go by stcredzero on Tuesday March 12, 2013 @07:44PM (#5365798)
> Rust and Go are not similar or competing.

Rust is more "kitchen sink" (done as elegantly and cleanly as possible) and Go is more minimalist.

Re:How We Went from 30 Servers to 2: Go by pcwalton on Tuesday March 12, 2013 @07:56PM (#5365845)
Being "kitchen sink" isn't a design goal of Rust. Rather, Rust is a lower-level, safer language. Go is higher-level.

Rust strives to be as minimalist as possible without sacrificing the goals of low-level control over memory and C++ performance (optional GC), memory safety, race-free concurrency, and type safety (no null pointers).

Re:How We Went from 30 Servers to 2: Go by duaneb on Tuesday March 12, 2013 @08:43PM (#5366041)
I don't think he meant kitchen sink, more that there are fundamental aspects from many parts of languages that are bound together well, which makes

> Rust strives to be as minimalist as possible without sacrificing the goals of low-level control over memory and C++ performance (optional GC), memory safety, race-free concurrency, and type safety (no null pointers).

somewhat funny.

Re:How We Went from 30 Servers to 2: Go by codygman on Wednesday March 13, 2013 @04:37AM (#5367431)
Why funny? (coming from someone who's thinking about giving Rust a try)
Re:How We Went from 30 Servers to 2: Go by duaneb on Thursday March 14, 2013 @12:37PM (#5376007)
He said "rust doesn't have the kitchen sink", and then listed the kitchen sink. Rust is awesome, you should use it.
Re:How We Went from 30 Servers to 2: Go by codygman on Thursday March 14, 2013 @01:14PM (#5376266)
Alright, I'll download the compiler/etc right now :D
Re:How We Went from 30 Servers to 2: Go by laut on Wednesday March 13, 2013 @12:42AM (#5366856)
Go is from 2009. Ruby is from 1995. Although it took about 10 years for Ruby to really start to be popular in the English speaking world.
Re:How We Went from 30 Servers to 2: Go by gnuvince on Wednesday March 13, 2013 @12:49AM (#5366868)
Rust, not Ruby.