I am a big fan of HtDP, and Felleisen's in-progress 2nd edition of HTDP is here: http://www.ccs.neu.edu/home/matthias/HtDP2e/ . It contains many improvements over the first (completeness however is not among them).
That said, HtDP's focus is very different from SICP, and I would not sequence one before the other. HtDP focuses on a methodology for writing robust maintainable software. It emphasizes specifications and testing and functional procedures.
SICP is focused on computer science and emphasizes much higher levels of abstraction - e.g. the *nix signal processing model, logic programming, constraint programming, stack machines and dealing with concurrency. It is more directly an introduction to Computer Science [despite Ableson's questioning the utility of the term 'computer science'] whereas HtDP is more of an introduction to the practice of programming.
Philosophically, SICP is ok with the idea of placing the student in over their head, e.g. the digital logic simulator and various mathematical examples treat digital logic and mathematics and banking as domain knowledge that the programmer might not have, but does not need in order to create sound abstractions.
[And Kickzales's course on Coursera was I awesome, I took the first version last summer.]
That said, HtDP's focus is very different from SICP, and I would not sequence one before the other. HtDP focuses on a methodology for writing robust maintainable software. It emphasizes specifications and testing and functional procedures.
SICP is focused on computer science and emphasizes much higher levels of abstraction - e.g. the *nix signal processing model, logic programming, constraint programming, stack machines and dealing with concurrency. It is more directly an introduction to Computer Science [despite Ableson's questioning the utility of the term 'computer science'] whereas HtDP is more of an introduction to the practice of programming.
Philosophically, SICP is ok with the idea of placing the student in over their head, e.g. the digital logic simulator and various mathematical examples treat digital logic and mathematics and banking as domain knowledge that the programmer might not have, but does not need in order to create sound abstractions.
[And Kickzales's course on Coursera was I awesome, I took the first version last summer.]