Erlang documentation always makes sense ex post facto
Erlang documentation always makes sense ex post facto. Rarely, if ever, ex ante.
Mind you, its a lot better than the usual lot...
Mind you, its a lot better than the usual lot...
Erlang, Binaries, and Garbage Collection (Sigh)
The nice thing about garbage-collection is that it is makes memory management absolutely transparent to you Of course, the above is true right up to the point when it stops being transparent, at which point it does a phase change from nice to clusterf**k of biblical proportions . There are entire posts, books, and suicide notes that have been written about this, and I have no great desire to add to them, save with the minor comment that paranoia about garbage-collection is still justified , albeit only in the edge-cases for most people. That said, I'll give you that Erlang GC is in many ways much, much better positioned in this regard than, oh, Java, but it still rears up and bites you in the butt when you least expect it. ( More information about Erlang's GC vis-a-vis Java here , and Jesper's truly excellent description of Erlang's GC here ). A story from the past should serve to illustrate this. Once upon a time, in a magical land far far away - well, Her
Comments