HandsOnRust VS command-line-rust

I'm working my way through the HandsOnRust book that guides you through creating a simple roguelike using Rust and Legion ECS. It's a really enjoyable experience so far, and I'm looking towards trying out Bevy ECS afterwards to compare the two.

https://github.com/thebracket/HandsOnRust

But if you really want to follow more things then hands on rust and zero to production are two good quality books for learning rust through game dev and web development respectively. But I would still urge you to try a few things by yourself first.

Started learning rust a while ago but I needed something to walk me through the features while building something useful. I discovered Hands On Rust and have learned more in 3 hours of building flappy bird clones than in two weeks of experimenting with tutorials.

There is Zero To Production In Rust which goes through building a webserver in rust from the ground up. Or Hands on rust for learning rust by building a game.

Some (optionally) in print: * Rust in Action * Programming Rust * Hands-On Rust * Rust for Rustaceans

Game development though might be a harder place to start. You may find other more basic areas easier to get going. Though there is a good book on learning rust with game dev Hands on Rust that you might find enough.

Other books/resources you might find helpful - Rust by example - a good compliment to The Book that shows concepts with examples. Though does not explain things as much. - Zero To Production In Rust - a look at webservers and taking them to production (still being written though) - Hands on rust - a look at introducing rust with gamedev. - Easy rust - Many more listed here

This is a beginner question. I'm following Hands-On Rust to build simple games. One thing that isn't clear to me so far is how `bracket-lib` actually load the fonts and image of different characters from a single PNG file. Is the PNG file segmented in certain pixel values so that `bracket-lib` could access each square of the image like an array? Does this mean that this PNG file must be always designed in specific ways? Thanks for helping!

One year ago, I released the first beta for Hands-on Rust. What a wild and awesome ride it has been! The book has been on the publisher's best sellers list for 50 of the last 52 weeks, since the print edition came out it's been in Amazon's top 10-20 for "C Language" and sometimes "Game Development" most of the time. I had a "good grief, am I famous?" moment when a relative (who works for one of the huge American social media companies) sent me a pic showing Hands-on Rust sitting on his boss's desk.

You absolutely must write programs, preferably using tests to ensure you are creating correct and reproducible code. May I suggest starting with my book, Command-Line Rust (O'Reilly, 2022). All the code/data/tests are in https://github.com/kyclark/command-line-rust Note that there are branches showing how to use the 4.x version of clap (command-line argument parser) rather than the 2.33 that was current when the book was published.

I think the best way to start learning a programming language is to write lots of small programs that you probably already know. Rust is a perfect command-line language, so I think it makes sense to start by implementing simple programs like "head" and "grep." I also think one should always learn to write and run tests, so I present my GitHub repo of inputs and tests you might like to use to write 14 such standard Unix command-line utilities: https://github.com/kyclark/command-line-rust If you want guidance on the language, I wrote a book called Command-Line Rust (O'Reilly, 2022) that explains all this code. One caveat is that the "clap" (command-line argument parser) module was at 2.33 when I published but is now v4, so you should look at the appropriate branches for versions of the programs that use the "builder" and "derive" patterns for that module. Or just use any old command-line parser you like as there's no requirement to use "clap." Best of luck to you!

You must write programs in a language in order to learn it. I also firmly believe that learning how to write and run tests is critical to learning any language. I wrote Command-Line Rust (O'Reilly, 2022) for the beginner (in Rust, at least) and with a focus on writing and testing small programs from very simple "Hello, world!" and getting increasingly more complex. You can look at https://github.com/kyclark/command-line-rust for the code/inputs/tests. Best of luck!

Code for the above book

I'm the author of Command-Line Rust (O'Reilly, 2022), which I wrote to introduce the language slowly to beginners by writing and testing short, focused programs. You can look over the code/tests/data at https://github.com/kyclark/command-line-rust. Note that there are branches that show the same programs using a more recent version of the "clap" crate.

I wrote Command-Line Rust (O'Reilly, 2022) to guide beginners in the language. You are challenged to write small functions and programs using tests to verify that everything is correct. You can look over the code and tests at https://github.com/kyclark/command-line-rust. Best of luck in your journey!

Here are the example programs from my book, Command-Line Rust (O'Reilly, 2022), along with the input files and tests: https://github.com/kyclark/command-line-rust

I like to suggest that students write programs they already know (or at least understand). For instance, you probably understand that head shows the first few lines of a text file, and you probably can already implement some version of that in one or two languages you know. Try that in Rust. I wrote 14 BSD/GNU command-line utilities in Rust for learning purposes. I wouldn't consider these high-performance/production programs as they are tailored to learning the language. I also stress how to test programs, so there are tests and inputs you can use to verify your programs match the output of the original programs (or you can modify these to suit your own tastes for how you would like them to work). https://github.com/kyclark/command-line-rust

Here are some more examples you may or may not find useful: https://github.com/kyclark/command-line-rust I tend to have a main() that calls a library's run() function that returns a Result and then exit with a nonzero code and error message on a failure.