News for hackers. Stuff that matters.
Re:Rust Priorities after 1.0 by kibwen on Thursday April 16, 2015 @11:13PM (#9392077)
Rob Pike has been working on Go's design since Newsqueak in the 90s, and further explored the same space later with Limbo. For reference, Newsqueak is a C-inspired language that features CSP for concurrency (which should sound familiar to Go programmers). Here's some example syntax (which should look familiar to Go programmers):

  a := mk(array[10] of int)
Given this lineage, it seems disingenuous to compare the ages of the two languages. Modern Rust is to early Rust as Go is to Newsqueak.
Re:Rust Priorities after 1.0 by andrewchambers on Thursday April 16, 2015 @11:16PM (#9392085)
This is true, but it does confirm my point about language flux potentially being a problem. It may work out nicely though.
Re:Rust Priorities after 1.0 by kibwen on Thursday April 16, 2015 @11:29PM (#9392110)
Indeed, it may ultimately turn out that modern Rust is to early Rust as Limbo (rather than Go) is to Newsqueak. I expect Rust will experience growing pains over the next few years as people begin employing it on an industrial scale and discover where the dark corners of the language lie. But nobody's saying that Rust will be the last systems programming language to ever be written. :)