If anything, I'd flip those two...<div><br></div><div>On the backend, things are anything but pure but it helps us reason about the program on the front end.</div><div><br></div><div>Laziness also isn't nearly as prevalent on the backend as it is on the front end.</div>
<div><br></div><div>Even though we can reason about things using purity and laziness on the front, the compiler often times makes an identical situation that runs a lot faster using strictness and mutation on the back.</div>
<div><br></div><div>/jve</div><div><br><div class="gmail_quote">On Thu, Dec 10, 2009 at 11:09 AM, John D. Earle <span dir="ltr"><<a href="mailto:JohnDEarle@cox.net">JohnDEarle@cox.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="padding-left:10px;padding-right:10px;padding-top:15px" name="Compose message area">
<div><font size="4" face="LM Mono 12">Laziness is on the logic front end and
purity is on the execution back end.</font></div></div>
<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>
<br></blockquote></div><br></div>