News for hackers. Stuff that matters.
Re:The Reliability of Go by pcwalton on Monday October 21, 2013 @01:40AM (#6583569)
The difference is that Erlang has process isolation: a panic is guaranteed not to mess up the state of any other process, because there is no shared state. This is what makes reliable self-repair possible. In Go, there is one giant shared mutable heap shared between all goroutines. So there is no guarantee that a panicked goroutine left the heap in an orderly state such that self-repair is possible.

Erlang actors and goroutines are very very different.

Re:The Reliability of Go by JulianMorrison on Monday October 21, 2013 @02:29AM (#6583713)
True. Although, panics do run defers, so with good coding practise it's possible to ensure that either you don't share things (but rather pass them around over channels) or things like locks are safely cleaned up.
Re:The Reliability of Go by masklinn on Monday October 21, 2013 @04:06AM (#6584047)
> with good coding practise it's possible to ensure that either you don't share things

So is it in C, that's no argument.

Re:The Reliability of Go by JulianMorrison on Monday October 21, 2013 @09:06AM (#6585195)
Turing completeness, your argument is invalid.

But seriously, it's not just possible to be memory safe in Go, it's fairly easy. You basically have to remember to never lock without defer mutex.Unlock() unless it can't possibly panic, and to share data via channels such that it only ever has a unique "owner".

Personally I'd have much preferred full isolation, immutable data with threadsafe mutable references, and Clojure style "persistent" collections which can be treated as values. But Go didn't go down that route.

Re:The Reliability of Go by Locke1689 on Monday October 21, 2013 @02:11PM (#6587212)
"All you have to do is call free with every malloc and always keep track of your array size. Geez, people, it's not that hard!"