3 ms·
I'm not very knowledgeable about either Erlang or Go. But from what I read, Erlang doesn't share objects between threads whereas Go does. This is a serious diff
by AndresNavarro 15y ago
I'm not very knowledgeable about either Erlang or Go. But from what I read, Erlang doesn't share objects between threads whereas Go does. This is a serious difference, because as the article mention you have to decide what to do if there are references from other threads. That's why the parallel with processes breaks in the case of Go. Cleaning up the resources of a share nothing (or little, and in a centralized place, see shared mem) process is easy and fast. Cleaning up the resources of a share most/everything thread... not so much.
- masklinn 15y agoBut that's the point is it not? TFA's building patterns to try to implement in Go some of the most basic facilities of Erlang, and try to work around Go's misfeatures (such as default shared memory). So the concepts described in TFA do indeed already exist in Erlang.
- AndresNavarro 15y agoIndeed. Erlang has this feature, I didn't intend to imply otherwise. What I meant was that this mechanism would be more difficult to implement in Go.
- masklinn 15y ago> What I meant was that this mechanism would be more difficult to implement in Go. Well of course, since it needs to be implemented in the first place whereas Erlang provides it as part of its core features.
- deleted 15y ago[deleted]