3 ms·
If my recollection is correct, some thought HTDP was an easier read than SICP. But now, there is a version of SICP adapted for Javascript: https://mitpress.mit
by clumsysmurf 4y ago
If my recollection is correct, some thought HTDP was an easier read than SICP. But now, there is a version of SICP adapted for Javascript:
https://mitpress.mit.edu/books/structure-and-interpretation-computer-programs-1 https://mitpress.mit.edu/books/structure-and-interpretation-...
Does the assertion still hold?
- sudopluto 4y agoi would rec HTDP, simply because DrRacket has some very cool tools for tracing recursive calls
- PeterWhittaker 4y agoI’ve not read HTDP, but I’ve been reading the JS SICP in dribs and drabs and find it very readable. (I’ve not read the original.)
- adamddev1 4y agoI found HTDP a lot easier to read and work through because it works through more "practical" problems (like building a game) whereas SICP gets into some pretty heady math based problems. Also see this article that explains how it takes a different approach to teaching recursion. I found this approach very understandable and helpful. https://parentheticallyspeaking.org/articles/how-not-to-teach-recursion/ https://parentheticallyspeaking.org/articles/how-not-to-teac...
- macco 4y agoYes it does. Scheme is not what makes SICP challenging. The sheer density of concepts is. HtDP is a bit repetitive and gets a bit boring over time. While some things overlap, I would recommend to first work through HtDP (or better through this online course https://www.youtube.com/channel/UC7dEjIUwSxSNcW4PqNRQW8w/about https://www.youtube.com/channel/UC7dEjIUwSxSNcW4PqNRQW8w/abo...) and then work through SICP - especially if you try to learn programming by yourself.