A few notes on choosing between Go and D for a quick project

[Walter Bright via Digitalmars-d]

On 3/13/2015 7:20 AM, Chris wrote:
> This is true. This battle is lost. But a lot of users, even people who are
> interested in D, shy away from D, because they don't have the feeling that "this
> is something really useful". We fail to communicate both its general usefulness
> and its strong points as opposed to other languages. What the big marketing
> machines behind Go etc. do is to make people feel good about a product (even if
> it's shit). We should do the same. Only because Google does it, doesn't mean
> it's a big taboo for us. The fact of the matter is that we have failed to win over:

I gave a talk at Digipen recently. (Digipen is a private college aimed at 
teaching professional game programmers.) They are mostly a C++ house. So I was 
talking to college students who were deep into programming.

I thought I'd try something different, and wrote a presentation that simply 
showed some neato things that D could do without diving deep into how those 
things work.

The home run, though, was showing how unittests combine with -cov testing to 
make code robust. Yes, you can do this in other languages, but it is so simple 
to do in D. It really struck a chord with these people.