Go, D, and the GC

[Martin Nowak via Digitalmars-d]

On Friday, 2 October 2015 at 11:27:12 UTC, Tourist wrote:
> I know that it has the reputation of being of the simplest 
> kind. Haven't looked at the code actually (and I wouldn't 
> understand much even if I did).

Go has a very simple GC itself. It's concurrent, so it trades low 
latency against performance (write-barriers) and throughput.
We wouldn't want to force everybody to use write-barriers, but 
you can avoid creating garbage in D much easier (e.g. map) and 
we're improving support for deterministic memory management. So 
while we keep on improving D's GC as well, GC performance is less 
of a problem in D b/c you have a smaller GC heap.