Go vs. D [was Re: Rust vs Dlang]

[Andrei Alexandrescu]

On 3/25/13 8:02 AM, Rory McGuire wrote:
> Perhaps it is actually just the "feel" of the debugging and
> benchmarking, and the general completeness of the *documentation*.
> This set of slides: http://talks.golang.org/2012/simple.slide introduces
> pretty much everything you need to know about Go. Graphs that show
> memory allocation
> by which function allocated, and the time taken of each function (d has
> a way to get the data as Walter points out). Ah the profiling was only
> mentioned in that slide set.
> The profiling doc is here:
> http://blog.golang.org/2011/06/profiling-go-programs.html
> It is all super easy, and documented so that you can do it now. All in
> one place. And I think possibly the most important thing about it is
> that it does what it says.
> The standard library all works together as a whole. Another thing which
> is different and makes Go easier or faster to pick up is that there is
> often only one way to
> do something. D excels in allowing a multitude of ways to do things.
>
> Do you know of any all encompassing slide set of document that one can
> pick up the information contained in
> http://talks.golang.org/2012/simple.slide? Is there an equivalent to
> http://blog.golang.org/2011/06/profiling-go-programs.html?

Thanks, Rory, these are good reads. We should get some articles too, we 
definitely have most of the technical pieces in place!

Andrei