I think the concurrency half is most important. Any non trivial &nbsp;Haskell program should leverage concurrency, and Haskell's concurrency is amazing.<div><div><br></div><div>Correct, it's not the only thing a person should know to write Haskell, but it is a required part of the curriculum. It also covers a lot of ground in demonstrating why Haskell is great.</div><br><signature></signature></div>
        <div class="gmail_quote nylas-quote nylas-quote-id-8r3wdvzcsj90j9le3866b8p5j">
          <br>
          On Jan 24 2017, at 8:59 pm, Joachim Durchholz &lt;jo@durchholz.org&gt; wrote:
          <br>
          <blockquote class="gmail_quote"
            style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
            <p>Am 24.01.2017 um 22:15 schrieb Joe Hillenbrand:<br />&gt; I _personally_ don't like LYAH, but I highly recommend Parallel and<br />&gt; Concurrent Programming in Haskell[1] especially the second half. It's<br />&gt; *required* reading for real world Haskelling.</p>
<p>Can you expand on that?<br />Both book title and synopsis seem to indicate that it is focused on <br />parallel programming, which is important but certainly not the only <br />thing you'd want to do in the real world. Also, not all real-world tasks <br />involve parallelism, so the claim that parallelism is required reading <br />requires substantiation.<br />_______________________________________________<br />Haskell-Cafe mailing list<br />To (un)subscribe, modify options or view archives go to:<br /><a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe">http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe</a><br />Only members subscribed via the mailman list are allowed to post.</p>
          </blockquote>
        </div>