command-line-rust VS book

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.

My first port of call was to google learn rust which lead me to "the book". The book is a first steps guide written by the rust community for newbies (or Rustlings as they're called) to gain a 'solid grasp of the language'.

Before Prodzilla, I’d read 'The Book' a couple of times, and had made my way through Rustlings, but hadn’t yet built a serious project in Rust.

To answer your last question;

Start with the Rust book.

https://doc.rust-lang.org/book/

Then do Rustlings until the syntax becomes muscle memory.

Then join the Discord and start doing little projects.

You won’t get up to the proficiency of other languages as quickly in Rust. It takes longer. For me it’s taking a lot longer, but I enjoy it.

Before diving into these repositories, familiarize yourself with Rust and its development ecosystem. The official Rust book is an excellent resource for developers at all levels. Each repository has documentation on how to contribute, covering code style, issue tracking, and pull requests.

This is my third Rust book after the official book and Rust in Action. The other two books are great, but they were too theoretical for me. I'm a slow learner and had much trouble grokking Rust's features and idiosyncrasies. When I was done with these books, I was lost and unsure of what I could do.

It's the same reason everything digital and downloadable isn't free: there's a cost to create it and there's a value to it.

For a language developer to charge for a book about that language, I think that's a completely valid way to make some money off of their work.

Even the Rust book, "The Rust Programming Language" is available freely online [0], but also as a print and ebook for sale via NoStarchPress [1].

[0] https://doc.rust-lang.org/book/

[1] https://nostarch.com/rust-programming-language-2nd-edition

You know you can just read it online right now in 2 different variants It does contain some systems programming.

I am looking at The Book (https://doc.rust-lang.org/book/), but hoped there was an amazing person on youtube.

Yeah, I'll build something, finally trying webassembly.

https://doc.rust-lang.org/book/ https://github.com/rust-lang/rustlings https://doc.rust-lang.org/rust-by-example/