12 Things to Help You Learn Rust

12 Things to Help You Learn Rust



The Rust programming language is gaining more and more momentum due to its memory safety features. Here is the first video in a new series about Rust starting with the basic things you need to understand like loops, variables, functions, tuples, strings and more!

What is Rust: 0:38
How to install Rust: 3:23
Println!: 4:29
Mut and mutability: 10:19
Shadow variables: 11:40
Constants: 13:49
Basic Types: 15:03
Strings: 17:05
Tuples: 20:08
Arrays: 22:35
Expressions and statements: 24:00
Functions: 26:39
Loop and while: 31:33
For loop: 33:13

Introduction to Android app development:

Let Me Explain T-shirt:

Twitter:
Instagram:

#garyexplains

#Learn #Rust

learn rust

Gary Explains,Tech,Explanation,Tutorial,Rust,Rust Programming Language,Memory Safety,Memory-safe languages,println!,mut,for,while,u128,i128,vectors,arrays,strings,integers,floating point numbers,functions,rustc,rust compiler

46 Replies to “12 Things to Help You Learn Rust”

  1. You're showing some fantastic breadth on this vid, Gary. I'm, foremost, a programming nerd and I've been following you for your hardware coverage and have been delighted with it for its accessibility. But I, myself, with a degree in computer science, am just beginning with Rust and I love it. They've run with the C++ community's long refined practice of RIAA memory semantics and have turned an art to a science with their fundamental build of a programming language atop it. It's amazing. The Rust-lang book is my homepage as I plod through it all. The borrowing tricks are very clever and to be completely honest, I wish there was a garbage collected version of the language so as to relax the learning curve so that the final jump to rust could be just laser focused on the borrowing and ownership stuff. It is real crazy and cool. I like garbage collection less and less as I reason through how graph algorithms absolutely destroy the CPU cache with frequent invalidations. And the CPU cache isn't just a nice-to-have on the side. Good performance can't be had without it.

  2. @8:07 i tried to replace those with strings and i noticed rust cares about what type of quotes i use, which is kinda wild. cause what if i need to make a template string on the web? i suppose i'll have to store it in those "" quotes as a string. looked more into it, its like bash where you can escape characters you need inside a string so thats good

  3. I am about a year into learning and using Rust, about as old as this video is. Now I can really appreciate why Rust has been the most loved language in SO surveys for 6 years running.
    On a management level, projects leaders like it because the compiler catches so many bugs, which means they can put more trust on every of their programmers (junior and senior) to produce reliable, bug-free code.
    On an individual level, programmers like it because of all the modern ergonomics Rust brings to the table – type inference, Python-like string templating, iterators, message channels, official build tool, world-class documentation, and so much more.
    And of course to tie it all together, the programs that come out is hella fast – nearly as performant as well-optimised C and Cpp, and leagues above interpreted languages such as Python. It's a language so good it only existed in people's dreams, right up until it actually happened.

  4. I would like to say that Rust is unlike other languages where you can learn as you go/while experimenting. I'd really recommend reading through the resources people mentioned before jumping in (steep learning curve).

  5. I know its not the niche of your channel, but can we please get a full Rust course 🙏🙏 This explanation was fantastic! The little things you mentioned on the side were actually very helpful in clearing many misconceptions I would have assumed initially. Please give us all of Rust you know 🙏🙏

  6. That's illegal! The first string you print in a language has to be "hello world!", not just "hello"… For twas so commanded in the sacred scrolls of computer science. This is blasphemy you have angered the computer gods whose wrath we all fear. As punishment, you will now spend eternity working on data formating protocols in the basement.

    😉

  7. I keep looking for a worthy challenger to overthrow c/c++ (rust, swift, kotlin-native), but I think c++ is keeping up with the times pretty well. For the most part, RAII is pretty straight forward (and safe).

  8. Every minute of this video is valuable … I have just started learning Rust this week; and I only know python (2 years experience)… and this video helped me a lot… please do more Rust programming stuff.

  9. I'm starting to learn Rust, but I'm wondering if the memory flaws in MODERN C++ are vastly overstated. For most projects it's a non-issue. How is anyone going to do a memory exploit of some silly game I develop, for example?

    Most systems programming is done in C rather than C++ anyway, So how can anyone say that C++ is vulnerable when it's not used that much in systems programming? It seems that someone has said that C is unsafe, and then thrown the baby out with the bathwater.

  10. This language is silly. Immutable variable? The whole point of variables is that they are, well variable. That makes as much sense as an unmovable car.
    Why do people come up with ridiculous languages to prevent programmer errors. Just learn to code properly. Overly nannying compilers lead to sloppy programming.

  11. Maybe I'm just old school but a "variable" that is immutable is better known as a constant. I really don't understand the point of this language pattern in rust, it's ridiculous.

  12. This is a great style of video! I'm curiously prodding around the outsides of Rust to see what it's like and this is a terrific introduction to core concepts and features without being overly verbose or lengthy

  13. If another coder can re-declare your variable without throwing an error, what’s to prevent that accidentally happening? (Expecting the next coder to be careful doesn’t count.)

  14. Got news that Linux kernel would support Rust to some extent like for writing modules. Came straight up here out of curiosity to know Rust 😂

  15. 9:40 lol, that's amazing.
    Why would they allow shadow variables ? That seems like not a smart idea.
    Expressions seems really dumb, for example why not have return ? And then I realized, this forces the return to be at the end of the function. That was not as stupid as it seems at all !
    Tip: with loop and while use a < > or instead of equal, so you know it will never end up in an endless loop in case you change some of the other code/calculations.

Leave a Reply