D benchmark code review

[Walter Bright]

On 12/14/2013 11:46 AM, "Ola Fosheim Grøstad" 
<ola.fosheim.grostad+dlang at gmail.com>" wrote:
> You could be right, I am only talking about the impression I am getting. "The
> smoke-signals being received from a distance". When you don't have one excellent
> compiler, but three in-the-works, it sends signals of a lack of direction and
> implies a lack of a leader that can rally everyone into something cohesive. This
> is not a critique of anyone, most programmers want to be creative and
> argumentative, not to "nurture", "manipulate" and "wave the whip" ( I am not
> even sure I like people who are "great leaders" ;^).

Back when there was only one D compiler, people said they wouldn't use it 
because there was only one. Now people won't use it because there are 3.

Essentially, if you want to find a reason not to use D, you'll find one. But if 
you want to use D, there are lots of reasons to. I personally find D to be 
satisfying and exciting to program in. I can get the code to look like the way 
the algorithm works in my head, and it runs fast, too.