News for hackers. Stuff that matters.
Re:Removing garbage collection from the Rust language by eru on Monday June 03, 2013 @05:20AM (#5812191)
> one distinguishing factor of GC (vs refcounting) is the need to "stop the world" during the mark phase.

That's a distinguishing factor only in practice. In theory there are real time garbage collectors.

Re:Removing garbage collection from the Rust language by bad_user on Monday June 03, 2013 @05:35AM (#5812229)
In practice there are also hybrids that try to delay long stop-the-world phases as much as possible, but still need to stop-the-world when compacting the heap, like JVM's CMS.

And I was under the impression that there already are GC implementations that never go into stop-the-world phases, like Azul's Pauseless GC [1]. There's also the new G1 from JDK 7 that promises to make pauses fewer and more predictable than CMS, while avoiding many memory fragmentation issues that CMS has (how well that works out in practice, remains to be seen, as it's not fully matured at this point).

Btw, I love how Rust is trying to solve memory management issues by reinventing the problem. That's what new languages should do, instead of reimplementing other languages poorly.

[1] http://www.artima.com/lejava/articles/azul_pauseless_gc.html

Re:Removing garbage collection from the Rust language by eru on Monday June 03, 2013 @06:21AM (#5812385)
On top of that, malloc (and friends) don't make any useful worst-case runtime guarantees either.
Re:Removing garbage collection from the Rust language by hga on Monday June 03, 2013 @10:36AM (#5813494)
That's very important to remember if your heap has a messy enough history.

The right language + a good GC can give you much better bounded worse case guarantees, with Azul's as the best I know of for an imperative language (the more functional, the easier it is to do a variety of things).

Re:Removing garbage collection from the Rust language by hga on Monday June 03, 2013 @10:31AM (#5813471)
Yes, there are ones like Azul's, and don't forget the copying GCs that have different characteristics than mark/sweep(/compact).