Hacker News Reader

I think a really cool tactic is racket's places, which basically creates individual zones running their own module with their own gc (but objects shared between cores don't take up extra space, there is a global table or something).

View on HN

This sounds very much like how Erlang does it - each process gets an isolated garbage collected heap and communication between processes happens through message passing.

How lightweight are Racket places? I'm not very familiar with the language, so I don't know if they're really comparable to Erlang processes.

Not lightweight at all really; a 1:1 mapping between places and cores.

How does that work? Either you have shared objects and you need a global garbage collector, or you don't. Using shared objects with a local GC results in memory leaks.

Reply on news.ycombinator.com