> D is pragmatic about memory allocation strategy, this fork won't be Better than a pragmatic approach to memory allocation is to not have to think about it at

> D is pragmatic about memory allocation strategy, this fork won't be Better than a pragmatic approach to memory allocation is to not have to think about it at all. For many applications, you can use the GC and not even know anything about memory allocation. If you embrace the GC, you make a lot more progress, since you can add things to the standard library and the language quickly and easily. Users not wanting a GC should use something else. Catering to users that don't want a GC imposes a big tax on everything and everyone. Embracing the GC doesn't mean they're going to strip out the reference counting and unique pointers already in the standard library.