Since this is actually the same edition that's been available for at least 7 years, but you still clicked the link, it's very likely you're interested in something along those lines. Consider getting "Concepts, Techniques, and Models of Computer Programming First Edition"[1] by Peter Van Roy and Seif Haridi. Although not exactly cutting edge (2004) and Oz-centric[2], still a great read and, for many, a fresh perspective.
Incidentally, in my opinion, The Rust Book was laid out exceptionally well for system programming beginners, at least in the state I read it through about 8 years ago or so. Steve and contributors managed to achieve a great balance between thoroughness and approachability of the text while dodging the curse of knowledge in a commendable way.
However, The Rust Book is as far from Concepts as it is from HTDP. It presents a specific language model in its relation to the hardware and common applications one faces while implementing what Concepts and HTDP teach to, well, design.
I agree. I don't recall exactly when I read it, but it was about 8 years ago, too. In that state, the Rust Book was very very good for people like me (i.e., had already learned many PLs).
Working through this was extremely helpful in getting me to think about building things with types, functions, and recursion. I saw an exponential increase in my problem-solving abilities after it. Can't recommend it enough.
HTDP teaches how to program. Philosophy does not. That's pretty much the entire difference, they're in different categories of books. Philosophy assumes you know how to program, and attempts to teach a way of programming. HTDP starts from the beginning with no assumptions about the reader's ability to program.
He's also the person behind Practical Typography [0], a great reference/guide for essential typography and layout concepts and terms. It has opinionated recommendations covering nearly everything you'll need to make beautiful documents like this one.
Particularly helpful is the practical advice: how to get the desired results in Word, Pages, or with HTML/CSS; not just high-level abstract guidelines. There's everything from keyboard shortcuts for inserting different dashes (to accompany the explanation on when to use each type) [1] to guidance on page margins in print and on the web [2].
At one point, I made my embedded API/package docs tool use Scribble.
For example, this document for a package is generated entirely from fragments scattered throughout the code, and package metadata: https://docs.racket-lang.org/roomba/
I am not quite sure what you mean. When I click the link and go to some page of the book, I see the usual interface of racket docs and such. I just see text on a web page. Do you mean the font? Or something else?
Yes, but also a lot of other things. It's important to direct the LLM to emphasize some embeddings vs others. This makes the chances of you getting good results exponentially higher.
But that would be supervised learning which we don't do (anymore) around here... honestly I wouldn't be surprised if the whole craze circles back to good old supervision, albeit many times empowered by what we have today on the shelves.
1. https://en.wikipedia.org/wiki/Concepts,_Techniques,_and_Mode...
2. https://en.wikipedia.org/wiki/Oz_(programming_language)
PS: I'll appreciate your recommendations as replies!