<div dir="ltr">> amount of work required to do this is much much more than amount of work required to write optimal C/asm code<br><br>I'm sorry, but no it's not. I've been using Haskell for a little under two years now, and I'm already able to produce programs with significantly less pain which outperform the C equivalents. Sure, if I pour a lot more time and head scratching into my C, then I can probably beat my Haskell, but I just don't have the time (or the need) to introduce pointer tagging, lazy evaluation, and referential transparency transparency to my C code.<br>
<br>Any way, this thread has lost any usefulness.<br><br><div class="gmail_quote">On Tue, Sep 23, 2008 at 5:32 AM, Bulat Ziganshin <span dir="ltr"><<a href="mailto:bulat.ziganshin@gmail.com">bulat.ziganshin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello Sterling,<br>
<div class="Ih2E3d"><br>
Tuesday, September 23, 2008, 5:13:57 AM, you wrote:<br>
<br>
> Oh, and it "simply and naively" loops with the following:<br>
> while (fgets_unlocked (line, MAXLINELEN, stdin))<br>
> If Bulat's point is that the shootout has inspired work on Haskell<br>
> performance, and in the stdlibs no less, then lovely, and that's all<br>
> to the good. Below every high level interface is lots of low level pain.<br>
<br>
</div>functions used to make C code faster is obviously worse than those<br>
used for Haskell code. just look - Clean gets 2x better performance<br>
than C<br>
<div class="Ih2E3d"><br>
> If his point is anything else, this is getting absurd.<br>
<br>
</div>my point is very simple - these tests says nothing about real<br>
performance since these tests was hardly optimized including adding<br>
special functions to ghc libs. amount of work required to do this is<br>
much much more than amount of work required to write optimal C/asm<br>
code<br>
<br>
and this work obviously doesn't speed up every Haskell program. so<br>
that we have in Haskell world now is heroic efforts to speed up<br>
shootout test which doesn't say anything about real Haskell<br>
performance. what we have on prcatice is 10-20% speedup of ghc 6.8 and<br>
several libs which may improve speed in some usages<br>
<font color="#888888"><br>
<br>
--<br>
</font><div><div></div><div class="Wj3C7c">Best regards,<br>
Bulat mailto:<a href="mailto:Bulat.Ziganshin@gmail.com">Bulat.Ziganshin@gmail.com</a><br>
<br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>/jve<br>
</div>