post on using go 1.5 and GC latency

[rsw0x via Digitalmars-d-learn]

On Saturday, 22 August 2015 at 06:48:48 UTC, Russel Winder wrote:
> On Fri, 2015-08-21 at 10:47 +0000, via Digitalmars-d-learn 
> wrote:
>> Yes, Go has sacrificed some compute performance in favour of 
>> latency and convenience. They have also released GC 
>> improvement plans for 1.6:
>> 
>> https://docs.google.com/document/d/1kBx98ulj5V5M9Zdeamy7v6ofZXX3yPziA f0V27A64Mo/edit
>> 
>> It is rather obvious that  a building a good concurrent GC is 
>> a time consuming effort.
>
> But one that Google are entirely happy to fully fund.

because Go is not a general purpose language.
A concurrent GC for D would kill D. Go programs saw a 25-50% 
performance decrease across the board for the lower latencies.

D could make some very minor changes and be capable of a 
per-thread GC with none of these performance drawbacks, but 
nobody seems very interested in it.