I read the abstraction chapter, but I really have a hard time translating those concepts to different languages like Rust. Seems like this book is very specific to this Racket-based teaching language?
The specific concepts in the book translate to other functional programming languages, and almost not at all to imperative programming.
The general thesis of the book, that you should follow a design recipe, is a universal one. It teaches you how to design your functions and write the documentation before you begin the implementation. This is also the part that students are the worst at, in my experience (as a TA for a first year course based on this book, twice).
isn't everyone?
as some one that worked for years as a trainer at a tech commercial training company, i eventually came up with two sort of realisations:
a) teaching HOW to program is really, really hard. i was never at all good at it, though i could teach programming languages and system architectures rather well.
b) when you start out, you cannot write too many functions.
i'm not sure that the book in question would entirely agree with this. any course using it for teaching would need lots of input from the physical human instructor.
…
a) teaching HOW to program is really, really hard. i was never at all good at it, though i could teach programming languages and system architectures rather well.
It really is a way of thinking. It takes deliberate practice to develop. Students are often uninterested in developing this kind of soft skill set because it doesn’t provide immediate returns when it comes to finishing assignments.
It’s a real shame. In the long run it pays huge dividends.
The preface explains the goals and ideas behind the book: https://htdp.org/2023-3-6/Book/part_preface.html
I actually think the materials in HtDP complements learning Rust pretty well. What makes Rust interesting exists almosy
Additionally you have to use generics and trait bounds extensively for some equivalent function in rust.
it's also move by default instead of copy, that saves memory copies which is a good thing?
I'm lost in 'clone everything', not a rust programmer per se.
Haskell takes the crown for modularity and safety but as a result it is less performant then rust.
Move by default is not modular. Why? Because it is a mutation. The state of your program changes after a move and your program must be structured around that.
That variable that was moved can no longer be reused in the same context so your program is less modular as a result as the definition of modularity is high reusability of modules.
Clone just means pass by copy. Make a copy and then pass the value. Pass by immutable reference works too. Just keep everything immutable for maximum modularity. But if you want to mutate things and keep things relatively modular then pass by copy (aka clone) is the best alternative.
All in all rust is typically harder to program for and harder to make elegant because of all the anti-modularity features used to increase performance and safety.