<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>Have you read the Guide?</div></blockquote><div><br></div><div><br></div><div>Caught again :-; Well I guess that when I first got acquainted with PLT scheme (in 2008 I think), having read (or reading in parallel) SICP, the former edition of Dybvig's book on scheme (or rather, the first parts of it) and perhaps some other stuff I don't remember right now, I thought I might skip the Guide... as a general read I mean; what I've always been doing is taking the links from the Reference to the Guide as an aid to understand... Perhaps also - I don't know - the Guide has become more voluminous, more PLT-specific in the meantime? Anyway I've had a look at the contents listing now and I see it contains lots of stuff I'll probably don't know or don't REALLY know. So I'll try to find the time to read it now!</div><div>(In fact, this is always the problem with the good suggestions of what to read or do one gets on this list - if only one had more than those 30-40 minutes a day for the whole ensemble of writing scheme code, reading scheme code, reading scheme documentation, writing emails to this list :-; ... not even to mention trying to go on learning Haskell:-; )</div><br><blockquote type="cite"><div>I'm curious to learn where precisely the hole<br>in the documentation lies. </div></blockquote><div><br></div><div>Perhaps there is none - but as you're going on in your mail yourself: People (me, at least) don't learn from documentation only. I read real books when I really want to understand concepts, get a broader view, .. and also, to learn by watching (some great books contain lots of code)</div><div><br></div><br><blockquote type="cite"><div>(Racket needs a book, but it has to be the<br>right kind of book.)<br></div></blockquote><div><br></div><div><br></div><div>Having quite a big (and thick!) queue of "must read" books on my desk right now, I've had to postpone reading it to the end yet another time, but the impression I've had from the first 200 (300?) pages of "Real World Haskell" was quite positive: It explains the core language, it gives a motivating introduction to functional programming (I remember being on vacation, without a laptop, when I read the section where it shows how to formulate functions in terms of foldl & foldr, and I tried doing the same in scheme in my head :-; ), but afterwards it really goes on to solving "real-world problems" in Haskell... </div><div>I think a book on Racket might be a bit like this. All the necessary stuff, Racket has already... the web server, the FFI, the network functionalities and and and... just present it not as a reference, but more of a tutorial / "by example" kind of thing?</div><div><br></div><div>Ciao, Sigrid</div><div><br></div><div><br></div><div><br></div><div><br></div><br><blockquote type="cite"><div><br>N.<br></div></blockquote></div><br></body></html>