cppreference-doc VS book

Rather than looking at good examples (which you should by all means do), add cppreference.com to you bookmarks and use it as your reference. By far the best C++ reference on the net. (from a C programmer who was thrown into C++ a decade ago -- slowly digesting C++20 now) Both StackOverflow.com and electronic.stackexchange.com are two additional QA sites that can help.

Sadly, not much. My method of learning is to get my hands dirty and waste a lot of time doing things wrong before I do them right. The only resource (outside of Google and StackOverflow) that I always had open was https://en.cppreference.com

In general, https://en.cppreference.com is your friend.

> As a C++ language reference I highly recommend https://en.cppreference.com

I'd be careful about such re-formulations of the Standard. When I was adding printf format checking to the D compiler, I discovered there were subtle discrepancies in the description of exactly how printf behaves. I went back to using the Standard.

Modern C++ code now looks very different to even C++11 code which is considered to be the start of modern C++.

"A Tour of C++" which has already been recommended is probably a good start to get back in the game. I think there was a new version coming out, but not sure what the current status about this is.

[https://en.cppreference.com](cppreference.com) is a good resource for me. It has documentation regarding the new standards as well and up to C++20 the examples are mostly complete, at least for the relevant things.

I can also recommend watching the "Back to Basics" talks on the CppCon youtube channel and once you are more familiar also the regular talks. They are great resources about practical topics.

Jason Turner's C++ Weekly videos are also a great resource. They are usually 10-15 minutes long videos that give you a good start to think about. Great way to learn something new every week.

At Google, at least, the style guide says to use snake case for variable names in C++ (but camel case for classes). As far as I can tell, this is also the convention in the C++ standard library.

Lets say that there's a file at https://en.cppreference.com/ called preferences.c. The command to download it would be wget https://en.cppreference.com/preferences.c

I would start with a direction of where to apply C++. Updating legacy code, working on embedded systems, creating financial application and creating high performant games are a few common option. Also sites like cppreference and Compiler Explorer/Godbolt are your friends in learning. CPlusPlus.com might help with legacy support as it stops with C++11.

Keep in mind that most YouTube C++ tutorials are garbage. Use www.learncpp.com instead as a tutorial, and https://en.cppreference.com as a language reference. Once you familiarize yourself with the language, you can learn the best practices using the C++ Core Guidelines.

The important thing to remember is that a concept exist and roughly what it's called, so you can look it up when you need to. You don't need to keep all the details in your head, that's what we have en.cppreference.com for.

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/