Things that keep D from evolving?

[Ola Fosheim Grøstad via Digitalmars-d-learn]

On Saturday, 6 February 2016 at 08:07:42 UTC, NX wrote:
> What language semantics prevent precise & fast GC 
> implementations?

This prevents fast GC: Pointers.

This prevents precise GC: internal Pointers + FFI.

Go now has <10ms latency for small heaps, <20ms latency for up to 
100GB heaps and <40ms latency for up to 250GB heaps.

But IIRC when calling a  C function in Go, the function called 
should not retain pointers or go down indirections?

https://talks.golang.org/2016/state-of-go.slide#37


So, basically, if you want fast memory release, forget using the 
GC in D.

> What makes it impossible to have ref counted classes?

Nothing.

> What are some other technical / design problems you 
> encountered? (other than poor implementation and lack of 
> resources)

Lack of focus on what most programmers expect from system level 
programming.