I regret having wasted my time trying to work through this about 2 years ago:<p>- There's a lot of sloppy content, i.e. misspellings that a spell checker should catch.<p>- Some code is syntactically incorrect. Some hasn't been ported over and is still in Scheme.<p>- The author's claim that the core points are present is somewhat dubious, since only parts of chapter 1 are reasonably complete.<p>- The difference in writing quality from the original text and what the author has changed is quite jarring. The original's prose is efficient, insightful, and deeply connected with other content. The new stuff is at best blog-quality.<p>- The author has certainly abandoned this project. Nor does it look like he'd be up to the task, even if he did have the motivation for it.
If you are interested in SICP, I'd definitely agree with the recommendation on that page to watch the videos.<p>The SICP book reads like an old maths textbook (not surprisingly) and is written to accompany the course, so just reading the book without watching the lectures is unnecessarily hard work.
It took me some time to figure out what they mean with "SICP". The author assumes that of course everybody knows "SICP" no need to tell you what it is. Now I realize it refers to the book "Structure and Interpretation of Computer Programs".<p>I can buy that book, now what is this project about, what are its goals? Why should I support it? What will I get from it?<p>There is probably a simple and worthwhile answer but I think that should be given at the very beginning of the presentation. The lost art of the "Abstract"?