Congrats on the new book!<p>Also some minor feedback: I know you're not supposed to judge a book by its cover, but obviously generated AI images give a lot of people 'the ick' so I'd recommend changing the cover (or modifying it).
I know this is just an early access, but it seems very underwhelming from the sample. This is all very basic Rust and the $35 price tag is not for an entry level book. You can literally read The Rust Book for free and it's more detailed.
So... why should I buy a $35 introductory programming book in 2024?<p>Here are some free introductory Rust books:<p><pre><code> - The Rust Book: https://doc.rust-lang.org/book/
- Rust 101: https://www.ralfj.de/projects/rust-101/main.html
- Rust by Example: https://doc.rust-lang.org/rust-by-example/
- Easy Rust: https://dhghomon.github.io/easy_rust/
- A Gentle Introduction to Rust: https://stevedonovan.github.io/rust-gentle-intro/
</code></pre>
Although I typically show people Rustlings, because it teaches programming workflow.<p>What am I getting for $35 that isn't covered excellently for free already?<p>Here are some books I spent money on in the last 5 years:<p><pre><code> - Functional Design and Architecture, by Alexander Granin
- Production Haskell, by Matt Parsons
- Thinking with Types, by Sandy Maguire
</code></pre>
Being a seasoned developer, I would pay money for someone to fast-forward me through advanced concepts.<p>Here are some examples of free Rust books covering advanced examples:<p><pre><code> - The Rustonomicon: https://doc.rust-lang.org/nightly/nomicon/
- Rust Design Patterns: https://rust-unofficial.github.io/patterns/
- Effective Rust: https://www.lurklurk.org/effective-rust/
- Rust Atomics and Locks: https://marabos.nl/atomics/foreword.html
- The Little Book of Rust Macros: https://danielkeep.github.io/tlborm/book/index.html
- Burn: Deep Learning Framework: https://burn.dev/burn-book/
- API Development with Rust: https://rust-api.dev/docs/front-matter/preface/
- Rust Compiler Development Guide: https://rustc-dev-guide.rust-lang.org/getting-started.html
</code></pre>
I'd pay money for any of those. Not sure about an introductory book, considering the availability of good, free books.
The samples are interesting, I wouldn't buy it (I just did the first few chapters of the rust book instead), but it seems cool. Get rid of the cover tho.
Hmm, hard to read on mobile (in portrait), had to zoom in a bit (but then text went out the window, so it was a bit of a balancing act)...<p>...so I rotate my phone.<p>DON'T DO THAT!<p>I'm directing that at both HN readers (you're welcome) and at the web author/admin (dude, TF?): a sudden explosion of additional content that I could not find a way to dismiss, when all I wanted to do was see the excerpts properly.<p>Seconding other comments re the poor quality crab, when your presentation is that poorly thought out and your prose that amateurish, it makes me want to save even more and dismiss this from my mind.<p>So thank you? I think?
> This is amusingly known as bebugging<p>I have never heard of this (though Wikipedia does say it was called that in the 70s).<p>I think this would actually be called "mutation testing".
I'm sorry to be a little rude, but the AI-generated cover (the left crab is missing an eye, for starters) is a negative quality indicator. If you weren't willing to take the time to put together a thoughtful cover, why should readers expect the book's content to be assembled any more carefully?