On Sunday, 12 January 2014 at 19:29:08 UTC, sunspyre wrote:
The very reliance of the garbage collector, regardless of how far between the stop-the-world sweeps are, is a showstopper for many people. They hear GC and think Java pauses. Being able to honestly claim "well it runs concurrently in a separate thread and doesn't[*] incur any performance penalty" would be the single biggest leap to greater adoption D could take at this point.
That is not technically possible. A truly concurrent GC has heavy penalty. People probably think of "Concurrent GC" has Microsoft calls one of the .NET GCs, which is "mostly concurrent".
The first step is get a precise GC. That should give a significant performance boost already. Everything else should probably build on this.
http://stackoverflow.com/questions/2583644/difference-between-background-and-concurrent-garbage-collection
