News for hackers. Stuff that matters.
Re:Fearless concurrency with Rust by elektronjunge on Friday April 10, 2015 @04:59PM (#9357076)
> Go was attempting to use only very-well-understood ideas to make a very-well-understood, simple language.

Many of the ideas in go were not well understood and had only been demonstrated in research languages prior to go. Its concurrency model and associated primitives, and the automatic interface system were in roughly the same state then as Rust's new ideas are now.

That said the ideas in Rust were not as well understood 5 years ago and I doubt that the go creators could have incorporated them well at the time. It took Rust 5 years of experimentation to come to what it is now (and its still got a number of additions to go!).

Re:Fearless concurrency with Rust by m0th87 on Friday April 10, 2015 @09:08PM (#9357959)
Go's concurrency primitives are rooted in decades-old research (CSP).

Its interface system is an implementation of structural typing, which may be even older.

You could maybe argue that neither had "industrial-strength" implementations, but that seems like a stretch.

Re:Fearless concurrency with Rust by f2f on Friday April 10, 2015 @05:37PM (#9357240)
> Many of the ideas in go were not well understood and had only been demonstrated in research languages prior to go. Its concurrency model and associated primitives, and the automatic interface system were in roughly the same state then as Rust's new ideas are now.

to Go's authors the CSP model was very well understood through three different implementations: Alef, Limbo, and Plan 9's libthread.

Re:Fearless concurrency with Rust by sanxiyn on Saturday April 11, 2015 @04:02AM (#9358854)
> Alef, Limbo, libthread.

Also Newsqueak.

Re:Fearless concurrency with Rust by jroesch on Friday April 10, 2015 @08:40PM (#9357901)
Maybe not well understood by programmers but in the programming language world Go's ideas have been around for over 3 decades.