[hamidreza-s]

Thanks for reading my post and taking time to write about it.

As the title of post which emphasizes on "WHY GC matters", I tried to reason why we should understand the underlying of a system, say Erlang, Go, Java or whatever else. But unfortunately always there are few documentation around about them and sometimes it is advised not to read them.

I do agree with you that comparing languages with very different goals is totally wrong, but what I did was comparing the Go's documentation author advice with mine, which is about being clever enough to understand your system.

[jerf]

The Go docs don't have that because they don't want you to know, they have that because they want to be able to change it without blowing up your programs.

Erlang has had similar corners over time, such as the way it has handled large binaries, where they've needed to reserve the right to change it. (IIRC the docs promise that the large binaries won't be in your process heap, which has been true for a long time, but beyond that, the details have changed significantly.)

[copsarebastards]

> The Go docs don't have that because they don't want you to know, they have that because they want to be able to change it without blowing up your programs.

That's a very charitable interpretation. If that's what they want to say, they could say that. I just don't buy it.