3 ms·
> I do really wish the designers had a bit more erlang experience. I feel the same way. I had this hope that this would be what I would learn instead of Erlan
by rdtsc 15y ago
> I do really wish the designers had a bit more erlang experience.
I feel the same way. I had this hope that this would be what I would learn instead of Erlang. You know it has goroutines and channels -- kind of like processes and casts. Well except that it is not the same. Erlang's processes that have explicit pids and messages are cast to those processes by referring to their pid, make a lot more sense to me than a bunch of channels. Maybe it is just me, but I really just prefer the Erlang way. (Is the the "actor" vs "CSP" paradigms?).
Then it is what you mentioned, exit signals. Anyone who wants to promote concurrency as first order feature in the language and expects it to be useful in the real world, would have to have something like supervision trees & OTP. In other words when you have lots of little goroutines doing stuff concurrently, it is expected some will just crash and then you'd want to do something reasonable, which is not always to just crash the whole application (OS process).
- enneff 15y agoGo is something quite different to Erlang, despite some small similarities. If you want Erlang, just use Erlang.
- uriel 15y agoI think Rob Pike discusses some of the differences between the Go and Erlang CSP-like models: http://confreaks.net/videos/115-elcamp2010-go http://confreaks.net/videos/115-elcamp2010-go