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).
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