Re:Removing garbage collection from the Rust language
by pron on Monday June 03, 2013 @12:09PM
(#5814037)
multi-object concurrency
Sorry. I meant multi-object transactions. Slip of the finger.
And let me qualify: good GCs that are relevant to solving that problem GCs are essential for, namely concurrent data structures. Erlang doesn't have a GC that's relevant (I really like Erlang, BTW).
Re:Removing garbage collection from the Rust language
by mietek on Monday June 03, 2013 @12:57PM
(#5814333)
Then surely you know support for transactions is built as a layer on top of ETS?
I actually don't like Erlang as a whole, because it lacks a static type system, but that's besides the point.
I reject characterising the BEAM VM's GC as not-really-good, especially in concurrency context. I believe the immutable, shared-nothing, message-passing model is a superior solution to the data problem than the threads-and-locks model. Actual memory sharing is an optimization which can be applied by the runtime system, as it's done for binaries in Erlang.
I'm not familiar with this term, and it doesn't seem googleable. Can you give a definition?
> The Erlang GC cannot be compared with Java's GC.
And yet, by saying "the only really-good GCs are found in the JVM", you compare all GCs.