I don't think it is slower, the real answer is 'it depends'; D's GC will only run when the GC needs to grow its buffer, so D's GC can be actually much faster than Go's

The problem however is, actually 2 problems:

- stop the world, nobody wants that in a world with lot of cores and threads

- it doesn't scale, the more pointers in your heap, it'll need to scan and traverse your WHOLE heap whenever it needs its buffer to grow, and that doesn't scale well

So it's good when you don't have much in your heap, and it starts to loose its benefits the bigger your program become, i wouldn't use it for my servers

But that's not the main problem of D, since the GC is optional, it's just not competitive with what's available in the market today

The people who want to drag D into the Java/C# territory are the problem in my opinion

D would be better if it focused being a system language, and took what C had to offer and put it to the next level, simplify the language, boost the existing features, allocators, pattern matching, tooling, compiler performance, hot-reload, binary patching

That's the thing i want to hear when there is a new version, not the endless GC topics