News for hackers. Stuff that matters.
Re:Dismissing Python Garbage Collection at Instagram by true_religion on Wednesday January 18, 2017 @09:47AM (#13426618)
ErlangVM's GC does exactly this. Memory is scoped in a closure around a process, and any time the process goes down all its memory its thrown away.

Also anytime a functions scope terminates, all its memory immediately goes away.

This can be done because its a functional language with immutable data structures.

Re:Dismissing Python Garbage Collection at Instagram by dsp1234 on Wednesday January 18, 2017 @02:26PM (#13429483)
I work in VBScript inside of classic ASP and the statement, "Also anytime a functions scope terminates, all its memory immediately goes away.", is true there. I doubt anyone would suggest that VBScript is a functional language with immutable data structures.

Additionally, all memory used by a page is cleaned up when the page is finished processing. This has to do with "Memory is scoped" more than immutable data structures.

Re:Dismissing Python Garbage Collection at Instagram by philosopheer on Monday January 23, 2017 @03:07PM (#13465461)
I think you mean memory usage is lexically scoped because no pointers to blocks are saved or returned? I think, and didn't really want to think harder, just thought in the same sense that functional brings some useful baggage with it, so does lexical scope.
Re:Dismissing Python Garbage Collection at Instagram by toast0 on Wednesday January 18, 2017 @04:51PM (#13430634)
> Also anytime a functions scope terminates, all its memory immediately goes away.

I don't think this is accurate; those values remain until GC is triggered for the process or the process terminates.

Re:Dismissing Python Garbage Collection at Instagram by PeCaN on Wednesday January 18, 2017 @05:13PM (#13430850)
Erlang's GC is the perfect example of ‘work smarter, not harder’. It's not a particularly advanced GC, it just does so little work that it's soft-real-time capable.

As usual, excellent prog21 article: http://prog21.dadgum.com/16.html (I miss prog21 already…)