December 11, 2009
Brad Roberts Wrote:

> This community has a lot of bad habits.  The particularly dangerous one demonstrated well in this thread is that of making assumptions about intent.  D isn't listed in the shootout, it once was.  We don't know the facts about why so we like to make the up.  Its human.  But it's really harmful.
> 
> Another really good example:  Silence on a top tends to be equated with rejection, especially when it comes to why whatever it was hasn't been implemented yet.  The majority of the time that's not the reason for the silence.. it's merely a matter of 'haven't gotten to it yet' or 'didn't see it amongst the hundreds of other things'.
> 
> Later,
> Brad
> 

The comment I made, I had talked to the author of the site and the reasons for not having D were not consistent with having Go on there.

And I do believe someone did have communication with the Shootout maintainer and the reason given was "too similar to C" which is also not consistent considering the choices of languages which it does include.

So I think it is safe to ponder on whether a bias is playing a role in these decisions.
December 12, 2009
bearophile:
> I think the notgentle person that manages the Shootout site has removed D because D programs were too much similar to the C programs.

I removed D because I started measuring on 4 different os/machine configurations instead of just 1 machine.

https://alioth.debian.org/forum/forum.php?forum_id=2839

I also removed a whole bunch of other language implementations and that upset lots of other people.
December 12, 2009
Bill Baxter:
> And Go qualifies because it has some CSP implementation built in?

Go qualifies for the moment - it's an experiment - maybe it'll turn out not to be so interesting after all, and in golang.org forums they'll speculate about why it was removed from the benchmarks game...
December 12, 2009
Brad wrote:

> This community has a lot of bad habits.  The particularly dangerous one demonstrated well in this thread is that of making assumptions about intent.  D isn't listed in the shootout, it once was.  We don't know the facts about why so we like to make the up.  Its human.  But it's really harmful.

+1
December 12, 2009
On Fri, Dec 11, 2009 at 4:55 PM, Isaac Gouy <igouy2@yahoo.com> wrote:
> Bill Baxter:
>> And Go qualifies because it has some CSP implementation built in?
>
> Go qualifies for the moment - it's an experiment - maybe it'll turn out not to be so interesting after all, and in golang.org forums they'll speculate about why it was removed from the benchmarks game...
>

Cool.  Thanks for popping in here to tell us that.

--bb
December 12, 2009
Isaac Gouy wrote:
> I removed D because I started measuring on 4 different os/machine configurations
> instead of just 1 machine.
> 
> https://alioth.debian.org/forum/forum.php?forum_id=2839

The link appears to be dead.
December 12, 2009
Walter Bright wrote:
> The link appears to be dead.

The link appears to work just fine from Mozilla Firefox.
December 12, 2009

Jesse Phillips  at "Fri, 11 Dec 2009 18:43:30 -0500" wrote:
 JP> The comment I made, I had talked to the author of the site and the reasons for not having D were not consistent with having Go on there.

 JP> And I do believe someone did have communication with the Shootout maintainer and the reason given was "too similar to C" which is also not consistent considering the choices of languages which it does include.

Is he trying to say that C++ is less similar to C than D?

 JP> So I think it is safe to ponder on whether a bias is playing a role in these decisions.

-- 
Best regards, Alexander Suhoverhov
December 12, 2009
Walter Bright:
> > https://alioth.debian.org/forum/forum.php?forum_id=2839
> 
> The link appears to be dead.

It's a little complex, you have to be logged in, or you have to accept some unsafe connections over a https. My suggestion is to ignore the whole thing and thread, you have better things to do.

Bye,
bearophile
December 12, 2009
"Isaac Gouy" <igouy2@yahoo.com> wrote in message news:hfurj4$1n9j$1@digitalmars.com...
> Walter Bright wrote:
>> The link appears to be dead.
>
> The link appears to work just fine from Mozilla Firefox.

I'm on firefox, and it's giving me some problem with the certificate.