ERRATA - The borrow checker is explained in my previous video "Rust makes you feel like a genius" (many people missed it) - Void functions actual return an empty tuple `()` which is pronounced "unit". - Reading a variable before it is initialised in C doesn't crash, it's undefined behaviour WHICH IS WORSE OMG - (1..) to my great disappointment isn't infinite, it's bound by the iterators internal i32, which is up to std::i32::MAX (2,147,483,647) - Missing semicolon on line 5! - i32 is difficult to liken to C's long, it's architecture-dependent. - 5:11 though this compiles, it should be `fn is_positive(&self)` to avoid the method taking ownership of the self doc.rust-lang.org/book/ch05-03-method-syntax.html - 2:35 - `assert!` should be `assert_eq!` - 9:31 `flat_map` or `map` both work in this example - 7:13 Error says `OErr` where it should be `Err`
The whole point of my channel :-) Here's a few more Rust videos of mine that I'm proud of, all in the same fast style: ruclips.net/video/oY0XwMOSzq4/видео.html
I thought I would be able to understand this video since it’s like “lesrn rust in 10 mins”, then he starts saying things like “MATCHES MUST BE EXHAUSTIVE”, WHAT THE FUCK DOES THAT MEAN?!?!?!
@@TheBlackmanIsGod btw if you are really curious, "exhaustion" in this context means "check all possibilities", when something is #[non_exhaustive], it means that you can't check for all possibilities and you need a "fallback" case
This is that video which assumes I am well versed in C, and now I want a quick crash course on getting up to speed with rust syntax. I rarely find tutorials like this. Every body starts a hello world program and spends 30 minutes there.
Not quite: - doc.rust-lang.org/std/iter/struct.FlatMap.html - doc.rust-lang.org/std/iter/struct.Map.html Basically map gives you ANOTHER iterator, and flatmap flattens out the nested iterators.
@@NoBoilerplate yeah so what I meant was that in this case they would give the same thing right? they wouldn't be a need to flatten I guess. I am just trying to make sure that the `flat_map` wasn't, for some reason, necessary in this particular case. Thanks for the tutorial. I'm finally deciding to learn rust.
@@brod515 Oh! I misunderstood, you're quite right! Both `map` and `flat_map` work for this case! Thank you for spotting that, I'll add it to the ERRATA!
Reading from undefined memory doesn't always crash at runtime. It's Undefined Behavior. Most commonly it either crashes or gives garbage data, but its allowed to do literally anything, including make demons fly out of your nose
This is exactly what I want to see in a tutorial! No 30 minute talk about every function a string has, but straight to the point while respecting my intelligence. Thank you!
@@NoBoilerplate I'd also love to have specific rust features explained in such concise and practical ways, i.e. traits, futures, working with cargo and toml, etc. Nothing too in-depth, just some mouth watering substance that gives you a good idea on where to start. (could basically do every chapter in the rust book like that haha)
This was incredibly helpful is what has helped me the most so far. I'm 'fluent' in several languages so I have a solid understanding of what to expect from languages. So many videos start from the ground up, and spend 10+ minutes explaining just a single concept or two. Skipping through video after video (or article after article) just to learn the basics is exhausting. That's why I appreciate this video so much. It's not to intended to be fully comprehensive but to provide people (like myself) a bridge between their existing knowledge and how to use Rust. I came away from this video feeling like I could write a nice simple 'hello world' type of application without having to look up 'how to write a function in rust'. Dense videos like these take a lot of time and energy to create, so just wanted to say a huge 'thank you' and share how much it's helped me. The resources that you've linked are just as helpful. Thank you!
My pleasure, and I'm so pleased the videos help you out! My aim is to get as many people into Rust as possible, because it's really revolutionary - not just for C developers tired with bugs (as the common wisdom is) but ALSO for high-level developers (such as me, a python web dev) wanting to write perfect code. Have you seen my previous videos? Rust has a steep initial learning curve. It's going to be a HARD job to get through a few pain points. Here's two you'll hit: 1. Two string types!? 2. Lifetimes And when you hit these rough days, you'll need a boost. My previous 3 videos are designed to remind you that not only is Rust exciting, but it's the only language you can do these amazing things in. Watch them when you need motivation. Good luck! (My recommendation is for 1. is to use String (not str) everywhere, and 2. you can sidestep by copying everything. .copy() .copy() .copy() who cares, optimise later! OR NEVER)
Math and programming are somewhat intertwined. Think of programming as "Math automation". You write the "math formula" as code, declare variables, and the computer "computes" everything else. Programming is a great tool for math majors especially if they had to deal with the same math formula with different variables.
Literally the point I hit the roadblock, its like the language is constantly trying to throw away everything you see unless you explicitly state that you need to keep it.
@@someonestolemyname what? That sounds like you gave up after 5-10 minutes of messing with references and move semantics, and never got used to it to see if it actually makes sense or not.
@@Anon.G and those safety restrictions means that you might end up in situations where you think it should work, because it would work in all other languages that you know, but it doesn't in Rust. This is even more confusing when you start composing your own types with structs and enums and they might contain (directly or indirectly) references and you need to be careful to place out all the lifetime annotations correctly. Furthermore, when you start including traits and heap allocations in to the mix then it can become a nightmare compared to other languages. Have you ever implemented a factory pattern in Rust? It took me over a day to figure out why my factories had to be singeltons for the borrow checker and lifetime checker to be happy.
Terrific: for someone new to compiling to web assembly using rust, I really appreciate how much you pack in. Agree that borrow-checker and lifetimes best separated out to another video. Rust is such a welcome evolution to programmers, improving the reliability of the programs we write!😀
3:04 void is very C-ish. Verbally "void" is... acceptable, but the top function here does not return "void". The type is actually called "unit" and written with the empty parens (). Just writing the notation correctly would be fine imo, but this should've had a short note that the top function is equivalent to -> () and explain that "unit" is just the empty tuple and has one value, and not some special type without any values used to denote no return value
Maybe, but I'd hazard a guess that the vast majority of programmers understand "returns void" as "returns nothing". C, C++, C#, Java and Typescript are all extremely common and well known languages so it's totally reasonable to use their terminology even if it's not technically correct for Rust (because ultimately it has the same effect).
This is so good, I'll be sending this to anyone who asks about rust! Have you thought of part 2 for things like lifetimes and the ecosystem (crates,cargo,docs,test)?
Very small correction : on most platform, long has 8 bytes, while int has 4 bytes in C and C++. Thus i32 refers to int or int32_t if you want to be really exact. Other than that, excellent video.
> int has 4 bytes in C and C++ Also incorrect. int is defined to be at least 16-bit whereas long is defined to be at least 32-bit. So while int is indeed 4 bytes on a lot of platforms, the standard doesn't define it that way.
I could be wrong, but I don't think that's the case. In Java, you would be right, int is 4 bytes, long is 8 bytes. In C/C++ though, long is 4 bytes, long long is 8 bytes, and int is determined by your architecture. If you're on a 32 bit computer, int is 32 bits aka 4 bytes. On a 64 bit computer, int is 64 bits aka 8 bytes. If you're somehow on a 8 bit computer, int is 8 bits aka 1 byte. The architecture thing is also like isize/usize in Rust
@@zperk13 I don't think I can link anything here, but let me quote Wikipedia here: > The minimum size for char is 8 bits, the minimum size for short and int is 16 bits, for long it is 32 bits and long long must contain at least 64 bits. You can also find these in the actual C standard here: 5.2.4.2.1 Sizes of integer types
@@zperk13 yes, this is the case on many embedded systems. There are lots of things like memory alignment and specialized instructions that are system compiler specific and make these subtle things like data type sizes a bit complex. It all comes down to the computer architecture.
Wow I feel better for getting this wrong - what complexity! You folks seem like you might know the answer to this: Is i64 faster than i32 on typical desktop 64-bit system? Another commenter said this. If so, maybe I should recommend i64s?
Every day's a school day! Yes, another commenter pointed this out, that's great news. I already use `const`s exclusively in my js, it's wonderful to know they're even safer than I thought!
It depends, some machine code generated by MSVC (and others) for x86 regarding i64 operations is inefficient and improperly considers microcode implementations
Thank you very much for you kind words. I don't know if I will do ads in the future, something on-topic in the middle of the video that is relevant to my audience perhaps. I suspect I could do more videos if I was sponsored - but I also find ads annoying! I'd love to know your opinion here, and thank you again.
Let me set the record straight: It's LISP and Haskell sneaking into the popular kids party wearing C's coat. Try out ruclips.net/video/4dvf6kM70qM/видео.html next and let me know what you think!
* cherry picking time * python: uses self notation, self is passed as an argument rust: uses self notation, self is passed as an argument python: has Self type (3.11) rust: has Self type python: has lambdas rust: has lambdas python: has match statement (3.10) rust: has match expression python: has async-await rust: has async-await python: supports custom event loops (things that execute async), unlike JS rust: supports custom event loops python: built-in C interface (as CPython is the most popular Python implementation) rust: built-in C interface python: has context management ( __ exit __ ) rust: has context management (Drop) python: supports b"bytes" syntax rust: supports b"bytes" syntax python: native support for AST modification (ast module) rust: native support for AST modification (procedural macros) python: has _ rust: has _
@@-parrrate counterpoints: a) I have dabbled in other languages for fun/uni but only really properly know python b) I barely know anything about rust (have never actually coded in it myself, only heard good things from friends) (but cool to know it has all those things too) c) it's a throw away comment on a yt video, I don't have the time or will to research everything I say 100% d) (not really a counterpoint) you mean nitpicking not cherry picking I think? Nitpicking is pointing out little flaws in something, cherry picking is deliberately excluding points that don't fit your arguement. (Tbf you can do both I guess but saying you're cherry picking a) doesn't fit and b) implicitly weakens your arguement)
@@-parrrate It's still very valid to say that Rust is a different way of thinking lmao. I've used Python and JS a fair bit and even with TS, I've still not had to worry about the particulars of `str` vs `String` or borrowing or ownership at all. There's a reason why the "higher level" languages are often used more by beginners.
Rust and python make good choices about many things. I've used python professionally for 15 years, but it's time to move on. The GIL is terrible for python's concurrency, and it benchmarks 80x slower than rust in single threaded tests. Python's ast does runtime modification, macros are compile time modification - a very different beast.
I've been writing python professionally for 15 years, and I think it's time for me to move on. Rust was just familiar enough for me to learn, but it took me a while. That's why I'm making these videos, do watch the others!
tuples were weird for me because python tuples are immutable but rust tuples are mutable, but man tuples are powerful, its like a struct but without needing to make one
@@NoBoilerplate I think so, too. Go relies a lot on Tuples since it doesn't have enums. After thinking more about it, I mainly use tuples when wrapping a type (New Type pattern afaik)
@@CunningBard Yeah, a pair of things is often OK for a tuple. In Rust, I find I'd rather name it and call it a Struct so that I know what KIND of paired data I'm working with. Javascript has made me afraid of anonymous blobs of data
I thought as a Java/C#/F# dev Rust would be really difficult to pick up and rather uncomfortable, like C++, but its really not as big of a leap as I thought.
I have been programming in different languages for 20 years+ and no language has ever made me fall in love again with creating software as much as Rust. If you code, you owe it to your heart and soul to check out Rust. Thanks for the amazing content in this channel by the way!
Wow, man! You are really awesome. I am impatient to learn Rust, but now it's gone to see this video. I know python anD JS. It's pretty similar. But very advance. I need a suggestion. I want to learn a language that gives me the best performance and flexibility to do anything and keeps me on-demand in the job market. Is that the Language that I need ???
You have two very strong languages, JS and Python. Top #2 at the moment in terms of popularity! redmonk.com/sogrady/2022/03/28/language-rankings-1-22/ I think learning Rust is a really good idea, it is already #19 in popularity, and I suspect already has a bright future too!
This video is truly awesome. Nowadays is very hard to find concise and good selected content about a language in only 10 minutes. We all know we won't learn the whole language in 10 minutes, but as someone who also just dives in the languages and takes its time to learn, this video cleared a lot of concepts about rust syntax (like reading and understanding the generics for functions and structs, or the '?' operator, or simply the '!' character that represents macros), it helps so much to understand what is written.
3:04 - I wouldn't write "f -> void" if i were you. I'd use the proper type, "fn() or fn() -> ()" for consistency, and further explain that "() is a struct with no values. it is a unit struct, because it can only have one state; existing. it means void.".
Oh gods we both have the same problem! I can't Google anything about rust (the language) without turning up new player guides, build reccomedatuon and sniper scope mods. A delight!
4:23 well except for wildcard imports ``use std::*;`` and the prelude items (including importing crates, ``std`` is available despite not declaring ``extern crate std;``)
Wonderful! I am delighted. Do watch my other videos (especially Rust is Boring) to get excited about WHY we are learning this complex language . The rust book is great too!
I sympathise! I recommend my previous 3 videos which are full of Rust concepts, and lighter on code. The goal of them is to get you excited enough to pay attention to the boring bits (that's what worked for me!) Good luck!
There's low demand for rust right now but I hope there will be. The language and tooling is excellent! I find that one can significantly cut down cloud computing and upkeep costs if they switch to rust. It's good for the environment as well. AWS has started to support more rust so I think we'll find more demand for rust soon.
Most of the Big Tech companies are in the Rust Foundation, so I would expect It to grow significantly over the next few years. WebAssembly may prove another sweet spot for high-perf applications in the browser client.
Owen! Thank you so much, you're so generous - but there IS another resource for rust: please do visit fasterthanli.me where the source of this video is taken from. Amos does SUCH great work on his site, he makes videos too, but his articles on Rust basically TAUGHT me the language! Thank you again :-)
@@NoBoilerplate I absolutely will! This is a great resource for people picking up the language. It can be hard to do that initial read-through of the rust book without your eyes glazing over a bit when you don't have the full context about why certain features can be useful or if the language is right for you. Being able to get a super quick set of examples like this showing how rust code works and some of the features is incredibly helpful as a primer for the rust book.
I would be very interested to get your take on Vlang and Zig, two languages that seem to be vying for a similar space as Rust. All three are meant to be extremely performant by ditching a Garbage Collector, but similarly avoid the gaping pitfalls of manual memory management. Of course, in most situations, it's not really accurate to say "X language is the best, objectively better than Y language." I personally lack the experience to do a full breakdown of what each language offers to the developer, which projects benefit the most from each language's best features, and so on.
oh COOL! I'd not read up on Vlang. Looks like a great little low-level language inspired by Go. HOWEVER it has a GC, which means I can already tell many things about the language: - No embedded development - Can't write linux modules - Imperfect for hard realtime applications (music, flight control software, ETL pipelines) - No borrow checker superpowers I wonder who this is for? A Go developer wanting lower-level code? Then why does it also have a GC? Hmm. Cute though! Zig I love - huge huge fan. It really helps you manage memory in a sane way, and the whole language has no surprises. But the kicker is you still must do it, and you might forget. Zig is certainly a better C, but they didn't try to push the envelope. Rust's lifetime annotations and borrow checker are a FEATURE, not a burden. A rich type system is great, but if you add lifetimes to the types, you've enriched them in ways that don't just mean the compiler can manage memory for you - you can build your own types with complex temporal logic in. One day I'll do a video on this XD
@@NoBoilerplate *Interesting!* I'd come across some performance benchmarks where Vlang would actually beat out Rust, and I found no mention of a GC, so I just kind of assumed there wasn't one. Impressive for them to reach that kind of performance with a GC, even if it's not really swinging for the same ball park. And I'd be very interested to see that video 😁
@@chrs-wltrs I admit I didn't get further than the front page, where they mention it! Apparently there's a new mechanism that can statically free 90% of memory cases, leaving the last 10% for GC. While that is terrific, I am left wondering how much time they're going to invest in an imperfect solution XD As for performance, Rust benchmarks in 1.1x C's speed (Java and JS are 4, Ruby is 20 and Python is 80). So while I can believe it, rust is fast enough!
This is almost C++17 in some strange syntax. I really like the idea of Rust and want to learn it. Coming from C++17 should be easy i thought. ( C++ from c++11 and up is just so easy to use and to use right ) But that is absolutely not the case. And it is not because of the concepts of the language which i really like. I get turned off almost immediately by the syntax and warnings about style. ( I use my own style :D ) Also it feels kinda restrictive. That might just be because I do not yet know the language, but using C++ I feel like I can write just about everything. With Rust its like hitting a wall every 40 minutes or something. But still a good thing and I´m going to invest some more time into this. Maybe some private Projects.
Cool! You're going to have a really fun time! My advice: Don't worry about syntax, every language has their own, and if you put 5 developers in a room, you'll get 10 recommendations for style! :-D Here's my video on how to learn: ruclips.net/video/2hXNd6x9sZs/видео.html
Hmm... From C++ to C# to DM to JS and TS, it's now time to learn rust. Surely I won't be bashing my head against a wall for the 5th time and I won't be trying to make a project that's way too complex for my skill level, right? Right? Who am I kidding, it's bashin' time!
It means the function receives read-only access to the argument. It's called immutable reference. There's also &mut which takes write access. Without any prefix, the argument is taken by value, which means the function consumes it (unless the type is Copy, in which case a bitwise copy is passed in).
@@robbietorkelsonn8509 It's becoming clear that the Object Orientation experiment has not been a wild success. Note that Reactjs and those like it use a functional reactive paradigm!
Fun, slightly annoying “oh crap now I have to consider that while writing unsafe {} code” fact: If you have unwinding enabled (by default it is) you can actually catch a panic!() with std::panic::catch_unwind()!
Very helpful content. I can’t even state how much I appreciate this format. Please make more high speed basics videos for rust. Or whatever. I’ll watch.
Thank you so much! I will. Video 11 (of this new format) arriving on Thursday. I may soon add another video, making my videos weekly, not on Rust, but on other interesting technical topics. Stay tuned!
Started software when big computer costing millions of us $ were having 512 Meg of memory...I am always say the same...You can learn a language in one week and you need 10 years to master it...there is NO shortcut and pain, hard work are the rule of the game.
I was confused by 3:30, where the "tail" of the declaration block is: "y + z". To the uninitiated, this almost looks like a function without a return type, and in other languages I've not seen this type of compound assignment. It took a moment of staring to realize the tail isn't a void addition that can be read by itself, but has to be resolved in your head then "returned" to the first line. It might have helped to put an example print statement or comment showing "x" is now "3". Cheers.
I'd heard of Rust, but didn't know what it was like. I didn't want to go through an hours long video describing every detail. I just wanted to get a sense of what it is like. This video gave me what I wanted. Thanks for doing the work.
My pleasure. This video focusses on the syntax specifically, which isn't quite the whole picture, check out other videos in my rust series, such as ruclips.net/video/4YU_r70yGjQ/видео.html
Thank you for the suggestion, noted! The article I've based this video on is much better than the video fasterthanli.me/articles/a-half-hour-to-learn-rust
Thank you so much! I'm having a great time writing these, and it's really helping solidify my own Rust knowledge (not least because when I make mistakes, people correct me!)
I think i'm gonna stay with c++, i don't wanna type so many "let" and "->" I learned to love the syntax " data_type var_name = value" This also remembers me of php and it's stupid dollar sign before any variable
Rust is extremely different isn't it! No inheritance, new syntax for lifetime annotations and borrows, and the compiler hates a lot of the standard normal patterns we've been using for decades. I know how you feel. Back in 2020 I crashed out of learning Rust twice. First time due to multiple string types (Haskell's biggest mistake made again, I thought to myself) and second due to lifetimes. At the time I had a great mentor who picked me up and helped me back on the path. Most people don't have this. This is why I made my Rust series. Yes Rust is very different from what you're used to. But that's the point. Two features you can't get in C++ that I think you'll like are Macros and the Unsafe system. Macros are nothing like templates or cmptime (they're more like lisp macros), and the unsafe system is a genius way to ring-fence pointer arithmetic, to allow us to build safe abstractions around unsafe pointer code. I did a video on both of them here, and I'd love your opinion on it: ruclips.net/video/PuMXWc0xrK0/видео.html Cheers!
I started learning Rust and then sorta gave up and just picked it back up only after rewatching your previous videos on Rust for motivation, this was perfect, thanks!
My friend, this warms my heart. My EXACT REASON for making these videos is because Rust was so hard for me to learn. I crashed out a few times, and only was able to get through it because I had a mentor helping me through it. I am hoping people can re-watch my videos for a boost!
@@NoBoilerplate Your videos are short but highly technical, usually there is a trade off between length and technical depth. For me personally it provides that quick motivation from a shorter video and gets my curiosity going because of the depth. I had seen the impl keywords but didnt know what they did in that short span where you explained tham, I opened up a temrinal and messed around with the impls. Keep them coming! You're doing a fantastic job
you can, but i think one might use let _ = get_thing(); if get_thing() returns a result, to make the unused result warning go away. personally, i use get_thing().ok(); because it’s concise and it’s like saying “it’s ok” but that’s something i came up with on my own and might not be a good practice, especially since it’s conceptually doing an unnecessary operation.
I feel that rust is one of those languages where you need a knowledgeable mentor in the early days. I had a go at writing sha256sum in rust, and there was a lot of head-scratching and digging around to find out how to do things. Whereas in Python and C it was relatively straightforward. I say mentor because, when writing 'worked examples', you're guessing what the novice programmer wants to write. But rather, you need to start with a novice programmer who knows what they want to write, and then guide them as to how to write it in Rust.
You've got it exactly right. Back in 2020 I crashed out of learning Rust twice. First time due to multiple string types (haskell's biggest mistake made again, I thought to myself) and second due to lifetimes. At the time I had a great mentor (Shout-out to Alex!) who picked me up and helped me back on the path. Most people don't have this. They need the excitement of my hype videos to break through. I will eventually run out of hype topics and move on to slightly more detail. But first, there's a few million developers I want to send to rustup.rs!
@@NoBoilerplate I've been learning rust recently, and chatgpt has been a great mentor. If I'm getting an error I can't make sense of, I can copy paste the offending piece of code and the error message, and like 80% of the time it tells me why it doesn't work. I still have to rely on traditional methods for the other 20%, but it greatly reduces the amount of head scratching I go through. It's been a bit of a challenge though, since nearly all of my experience is in C# and Python. I've never used a low level language before, so the learning the intricacies of low level + the intricacies of rust simultaneously has been challenging. I've come pretty far though!
@@sa1t938 oooh that's INTERESTING! I'm in deep with chatgpt, and I'm SUPER excited and scared for what 2023 is going to be like, with this tech revolutionising every single field!
I find writing C unbearable. Too low level, too much UB and too little abstraction facilities, unless you (ab)use the preprocessor. C++ is kind of OK but a real beast to tame...
I might have invented that, though there is a doc.rust-lang.org/std/slice/struct.Split.html I copied Amos's examples for the video here fasterthanli.me/articles/a-half-hour-to-learn-rust perhaps that particular line is psudocode?
@@NoBoilerplate between these videos and Lost Terminal, allow me to politely but strongly disagree, you deserve all these subscribers and more! Humility is a great thing but don't down play your good work unnecessarily either 😊😊
@@NoBoilerplate Well, you seem really quite skilled at condensing complicated topics down to understandable, short videos. The closest example I can think of would be Fireship or (, though it’s not on the same topic,) CGP Grey. For reference, they have 1,4M and 5,43M subscribers respectively. Until you have at least a hundred thousand, I’d consider you underrated.
Come from JavaScript. Sigh didn't like typescript still need to learn about the type data and other things. Knowing to code correctly and understand take time to think correctly.
Typescript and Rust are the two most loved languages in the world (according to the stack overflow developer survey) and I think it's because they both are used by people who value correctness. Check out my latest video in my Rust series on this ruclips.net/video/4dvf6kM70qM/видео.html
@@NoBoilerplate Never tried it, but I plan to soon. It looks awesome. It's like Electron but using much lighter weight Rust for backend, glue logic, and a browser-like front end interface. It claims to have the ability to glue other runtimes into the same binary, like Node.js, Julia, and Python, to mix and match polyglot tech stacks relatively easily. I've been intermittently looking into whether I can use it to have Python & Pyscript do the front end UI stuff, with Rust in the back end to handle all the heavy data crunching and OS interactions, while sidestepping the staggering binary size & memory footprint bloat that comes with using chrome/electron. It seems possible. As soon as I can make the time I really want to make a network mapping tool, because Visio is a crime against UX design, and it's looking more and more like Tauri would be the best way to do native application development.
This is being used in the Linux kernel now?! Ugh, this seems like a disaster waiting to happen - If you can't write a functional application in C or X86 Assembly then you should *NOT* be writing linux kernel drivers. At least it isn't full of Object-Oriented crap where developers tend to just write awful Java and give it a .cpp file extension.
Your faith in the intelligence of C developers is not shared by Microsoft, Google, or the OpenSSL team. They experience the growing pains of the language's flexibility: Once your program becomes non-trivial, it appears to be impossible to avoid memory nightmares, which manifest as security holes so terrible that we give them names: Slammer worm, WannaCry, Trident exploit, HeartBleed, Stagefrieght, Ghost Rust is as strict as you wish other C developers were. I'm not excited by rust because it's flashy, I'm excited by it because it's boring. Here's my video on this topic, I'd love your thoughts ruclips.net/video/oY0XwMOSzq4/видео.html
i was looking for this thank you for making this video if possible please make a series of tutorial for rust for the people who already know some programming language
I’ve only started learning to code about 5 months ago , of course with html and css and then JavaScript and I’ve mainly been focusing on JavaScript now , but watching this it seems hard maybe this video is fast too and as a beginner a bit over my head , some of it. But my question. Is , does anyone have recommendations on learning rust as a beginner ?
I sure do! Apart from the source of this video (check the description for the much better article I based it on), try: - github.com/rust-lang/rustlings - and read doc.rust-lang.org/stable/book/ Rustlings starts off REALLY slow, you'll be very comfortable. The book also is written very well, doesn't assume a software background. And do ask questions in #newbie-advice in the No Boilerplate discord, links on noboilerplate.org! Good luck!
I'm trying to create a programming language and I can't decide between using c++ or rust. I've tried doing some stuff in both, but it was a little difficult to do what I wanted with rust. No classes, can't assign references in structs without destroying the code with lifetimes and had many other problems while learning rust
Rust is certainly more difficult to learn, but it is WORTH IT! Have you watched my other videos on rust? In them I explain the unique features that you won't find anywhere else.
Yes, this is typical experience when starting to learn Rust, particularly for people coming from OOP. Rust is not the kind of language where you learn to translate syntax from language X, and you're good to go writing your code in whatever style you like. Rust has its own "coding paradigm", that's somewhere in between functional, OOP and imperative. You tried to do some stuff in Rust, and it was difficult to do what you wanted, THE WAY YOU WANTED TO DO IT! That's the problem. It took me about a year to learn the "Rust way of doing things". Unfortunately, I still can't fully explain what that is exactly. Especially not in a single youtube comment. People describe it as "becoming friends with the borrow checker", but never really describe how to get there.
@@NoBoilerplate Of course I did. That's why I decided to learn it :) It is great because you can make no mistakes in your runtime because of rust if you use it the right way, it will have a difficult learning curve because of that, but like you say: it's worth it.
@@KohuGaly A year of learning is too extreme for me. I think I can learn it quicker, thanks to modern IDEs, but if it's worth in the long run, that's another question
I know im hitting this a bit late but do you have any Rust video course suggestions? I don't learn well by going through written books or general written content.
I certainly do, my recommendations on how to learn Rust are here: ruclips.net/video/2hXNd6x9sZs/видео.html Though the Rust Book might not be for you, my recommendation of Rustlings will be - it's the best way to learn Rust!
On one hand, the compiler being this pedantic over almost all the things is fantastic since most "throw away code" is something you actually NEED to throw away and some crude prototyping can happen during compile time instead of runtime. On the other hand, I think you can make some specialized logic based reprap that creates stubs and fake integrations before you move onto creating the "official integration" in some other language that maybe less concerned with some forms of errors that _may_ be caught in Rust before deployment. At least you won't have to deal with the type signatures made famous in that "American Psycho" business card parody of Rust functions from theSTEMgamer XD
If you can create a lambda calculus in Prolog, you can also create dependent types in this language. maybe_fopen(_, _, -1, invalidFile(E)) :- E = 'Could not open file'. maybe_fopen(PATH, FLAGS, FD, RESULT) :- ((string(PATH), string(FLAGS)) -> (integer(FD) -> RESULT = validFile([PATH, FLAGS, FD]); RESULT = invalidFopenReturn('File descriptor must be integer != -1')); RESULT = invalidFopenArgs('Path and Flags must be strings')). When you query for the result of this call like: ?- maybe_fopen("/tmp/foobar", 36, -1, R), print(R). You now get ALL the possible ways this specific function call with these specific arguments can fail, including the -1 file descriptor AND the invalid argument types. I'd say Prolog and similar constraint solvers in the logic programming space are one of the better tools for high level blueprint coding that can also be interactive since prolog can import and run these scripts inside of a REPL. This might be a great starter for automatically generated tests with functions/predicates in this kind of dependently typed domain, since it's cheaper to change the code up front at design time rather than review/production release time. Jarble's transpiler on github and Warren's abstract prolog machine would be great study materials if you're more interested in the topic.
I liked the idea of rust but have no experience with it I loved when I used functional features like match case and expression instead of return in Scala This video makes so much sense, thank you. I like Rust now, just need to convince the boss typescript isn't the answer to everything
Typescript is certainly 100x better than plain Javascript! But yes, ideally you'd get some rust in. Have you seen my previous videos? The "perfect" and "genius" videos might persuade your boss :-)
Thank you! All my videos are like this, here's another in the playlist if you've not seen it, I'd love to know what you think: ruclips.net/video/sbVxq7nNtgo/видео.html
I also like the short and dense format, although I felt there were places where the examples were confusing for beginners and a bit more explanation would have been very beneficial. For example, I wish the video had explained what |c| meant.
Rust could have featured a beautiful and concise syntax like C but they had to go mess everything up by adding clutter like 'fn' and reverse variable type declarations etc.! For example: fn greet(name : String) { println!("Hi {0}!", name); } should simply have been: greet(string name) { printf("Hi %0!", name); } . It is the lack of straightforwardness and little details like this that makes rust a terrible mess! Every Rust example that I see I can convert into a much simpler and more beautiful and clutter free C like syntax! These new language developers simply do not care!
@@NoBoilerplate Of course there are new features and new paradigms in a new language like Rust but that does not mean you can't keep the language concise like C which is the golden standard of concise languages.
That's a very useful video, although, I didn't understand most of it, lmao. At least now I will go to the rust book and read it all, because what you showed is peeking my interest a lot
@@NoBoilerplate Yes, I watched every of your Rust related videos and really enjoyed them, that is why I got recommended this video. Thanks so much for making them btw
|n| {n +1} is the anonymous function syntax in rust, same as ruby. The first part define the parameters, the second part is the function body. You'll see them a lot in In the iterator methods like map
It is isn't it! That's mainly because of two big features that Rust has that C# (I believe) doesn't: - Lifetime annotations (for modelling not just WHAT your data is but WHEN) - References & borrowing. This is the secret sauce that allows you not just to not have a slow GC, but unlocks the Fearless Concurrency that Rust is famous for! It's an investment, for sure. But take a look at a few other videos in my series, and you'll see magic that you can't get anywhere else! Playlist here ruclips.net/video/Q3AhzHq8ogs/видео.html
ERRATA
- The borrow checker is explained in my previous video "Rust makes you feel like a genius" (many people missed it)
- Void functions actual return an empty tuple `()` which is pronounced "unit".
- Reading a variable before it is initialised in C doesn't crash, it's undefined behaviour WHICH IS WORSE OMG
- (1..) to my great disappointment isn't infinite, it's bound by the iterators internal i32, which is up to std::i32::MAX (2,147,483,647)
- Missing semicolon on line 5!
- i32 is difficult to liken to C's long, it's architecture-dependent.
- 5:11 though this compiles, it should be `fn is_positive(&self)` to avoid the method taking ownership of the self doc.rust-lang.org/book/ch05-03-method-syntax.html
- 2:35 - `assert!` should be `assert_eq!`
- 9:31 `flat_map` or `map` both work in this example
- 7:13 Error says `OErr` where it should be `Err`
It would be helpful if this was pinned. Great video by the way.
Have you ever heard a language called "vlang" ?
@@user-rg1jp2us4o Thank you - pinned. This is the SECOND time I was sure I pinned a comment and youtube has forgotten about it. HMM
@@mixwood1130 I've not! (which is already a problem lol) But it'd love to hear about it?
C could crash, but sometimes it doesn't and that's actually worse too.
You explained (atleast to an experienced programmer) everything necessary about Rust in 10 minutes, that's something that others do for 2 hours!
The whole point of my channel :-) Here's a few more Rust videos of mine that I'm proud of, all in the same fast style: ruclips.net/video/oY0XwMOSzq4/видео.html
walked in thinking this was about the videogame rust, walked out being able to hack the pentagon.
ha! I have the reverse problem all the time XD
@@NoBoilerplate At least now you know how to raid a base with Double Barrel Shotguns and C4
I thought I would be able to understand this video since it’s like “lesrn rust in 10 mins”, then he starts saying things like “MATCHES MUST BE EXHAUSTIVE”, WHAT THE FUCK DOES THAT MEAN?!?!?!
@@TheBlackmanIsGod btw if you are really curious, "exhaustion" in this context means "check all possibilities", when something is #[non_exhaustive], it means that you can't check for all possibilities and you need a "fallback" case
@@crimsonmegumin thank you for that but I’m still totally lost and that doesn’t make any sense to me.
This is that video which assumes I am well versed in C, and now I want a quick crash course on getting up to speed with rust syntax. I rarely find tutorials like this. Every body starts a hello world program and spends 30 minutes there.
I'm a massive fan of getting straight to the point and getting rid of boilerplate, great video and style!
Thank you so much! Did you see my previous 3 rust videos? They're even FASTER!
@9:31 I'm assuming `flat_map` was just used as an example and `map` could have achieved the same thing.
Not quite:
- doc.rust-lang.org/std/iter/struct.FlatMap.html
- doc.rust-lang.org/std/iter/struct.Map.html
Basically map gives you ANOTHER iterator, and flatmap flattens out the nested iterators.
@@NoBoilerplate yeah so what I meant was that in this case they would give the same thing right? they wouldn't be a need to flatten I guess. I am just trying to make sure that the `flat_map` wasn't, for some reason, necessary in this particular case.
Thanks for the tutorial. I'm finally deciding to learn rust.
@@brod515 Oh! I misunderstood, you're quite right! Both `map` and `flat_map` work for this case! Thank you for spotting that, I'll add it to the ERRATA!
If I use i32 for everything, the app will consume a lot more memory, or the compiler this can somehow fix that?
Yeah, a few bits here and there. But very likely you'd never notice. And if you do, you have alternative optimisations 😄
Reading from undefined memory doesn't always crash at runtime. It's Undefined Behavior. Most commonly it either crashes or gives garbage data, but its allowed to do literally anything, including make demons fly out of your nose
You're right, it's WORSE than crashing! The more I learn about cpp the sadder I am 😂
@@NoBoilerplate common experience
not the demons again...
@@VixieTSQ no known implementation has chosen that option.
"Undefined Behaviour is a good thing actually"
- The C++ cope fiend
This is exactly what I want to see in a tutorial! No 30 minute talk about every function a string has, but straight to the point while respecting my intelligence. Thank you!
That's what I'm here for - fast, technical videos! What would you like me to do next?
@@NoBoilerplate More Rust, maybe ideas of projects to try out
@@rachydamine9458 Righto!
@@NoBoilerplate
I'd also love to have specific rust features explained in such concise and practical ways, i.e. traits, futures, working with cargo and toml, etc. Nothing too in-depth, just some mouth watering substance that gives you a good idea on where to start. (could basically do every chapter in the rust book like that haha)
@@erifetim righto! Sounds good, noted!
I'm only here to get a gist of what Rust is about, but I gotta say, "it panics when it unwraps and finds an error" is a wonderfully vivid image
Like a skittish horse!
Here's my high-level overview of Rust ruclips.net/video/4dvf6kM70qM/видео.html
This was incredibly helpful is what has helped me the most so far. I'm 'fluent' in several languages so I have a solid understanding of what to expect from languages. So many videos start from the ground up, and spend 10+ minutes explaining just a single concept or two. Skipping through video after video (or article after article) just to learn the basics is exhausting. That's why I appreciate this video so much. It's not to intended to be fully comprehensive but to provide people (like myself) a bridge between their existing knowledge and how to use Rust. I came away from this video feeling like I could write a nice simple 'hello world' type of application without having to look up 'how to write a function in rust'.
Dense videos like these take a lot of time and energy to create, so just wanted to say a huge 'thank you' and share how much it's helped me. The resources that you've linked are just as helpful. Thank you!
My pleasure, and I'm so pleased the videos help you out!
My aim is to get as many people into Rust as possible, because it's really revolutionary - not just for C developers tired with bugs (as the common wisdom is) but ALSO for high-level developers (such as me, a python web dev) wanting to write perfect code.
Have you seen my previous videos?
Rust has a steep initial learning curve. It's going to be a HARD job to get through a few pain points. Here's two you'll hit:
1. Two string types!?
2. Lifetimes
And when you hit these rough days, you'll need a boost. My previous 3 videos are designed to remind you that not only is Rust exciting, but it's the only language you can do these amazing things in. Watch them when you need motivation.
Good luck!
(My recommendation is for 1. is to use String (not str) everywhere, and 2. you can sidestep by copying everything. .copy() .copy() .copy() who cares, optimise later! OR NEVER)
@@NoBoilerplate the Copy trait is marker. you meant .clone()
@@malbacato91 Ah! Thank you!
too long should be 5min
Welcome to the rust community :) if you want a concise language may I suggest another
@@connormc711 I'm too impatient to do that
@@TegridyMadeGames you should practice patients I have found it too be more helpful than any tutorial
@@connormc711 can you summarize that sentence? Too long to read.
watch on 2x speed
0:56 variable binding
1:23 choose integer type
2:14 tuple
4:43 struct
5:42 funtion
8:20 question mark operator
8:36 Iterator
Good job!
thanks
I usually run videos on 1.5x speed. This was a mistake.
gotta go fast!
Did I just join a cult
Set the playback speed to 2x and it'd be 5 minutes instead of 10
These videos are for people like us 😂
learning rust in 5 minutes frfr
I've literally just watched it like that lol
As a math major in Uni, Rust notably reads a lot like advanced mathematics. Especially with the "let" keyword and infinite iterations
You're gonna love Haskell :-)
Math and programming are somewhat intertwined. Think of programming as "Math automation". You write the "math formula" as code, declare variables, and the computer "computes" everything else. Programming is a great tool for math majors especially if they had to deal with the same math formula with different variables.
You avoided the single most confusing part of Rust that is the most different from other languages: the borrow system and lifetime annotations
Literally the point I hit the roadblock, its like the language is constantly trying to throw away everything you see unless you explicitly state that you need to keep it.
The borrow system is literally just pointers/references from any other language + a few safety restrictions.
@@someonestolemyname that's literally what it does. are you perhaps a undergrad or hobbyist?
@@someonestolemyname what? That sounds like you gave up after 5-10 minutes of messing with references and move semantics, and never got used to it to see if it actually makes sense or not.
@@Anon.G and those safety restrictions means that you might end up in situations where you think it should work, because it would work in all other languages that you know, but it doesn't in Rust. This is even more confusing when you start composing your own types with structs and enums and they might contain (directly or indirectly) references and you need to be careful to place out all the lifetime annotations correctly. Furthermore, when you start including traits and heap allocations in to the mix then it can become a nightmare compared to other languages. Have you ever implemented a factory pattern in Rust? It took me over a day to figure out why my factories had to be singeltons for the borrow checker and lifetime checker to be happy.
Coming from several back-end languages, this video was exactly what I needed to get me started with Rust. Thank you!
My pleasure! Check out my other videos for inspiration!
Terrific: for someone new to compiling to web assembly using rust, I really appreciate how much you pack in. Agree that borrow-checker and lifetimes best separated out to another video. Rust is such a welcome evolution to programmers, improving the reliability of the programs we write!😀
3:04 void is very C-ish. Verbally "void" is... acceptable, but the top function here does not return "void". The type is actually called "unit" and written with the empty parens (). Just writing the notation correctly would be fine imo, but this should've had a short note that the top function is equivalent to -> () and explain that "unit" is just the empty tuple and has one value, and not some special type without any values used to denote no return value
Thank you! I have added this to the ERRATA pinned comment.
Maybe, but I'd hazard a guess that the vast majority of programmers understand "returns void" as "returns nothing". C, C++, C#, Java and Typescript are all extremely common and well known languages so it's totally reasonable to use their terminology even if it's not technically correct for Rust (because ultimately it has the same effect).
This is so good, I'll be sending this to anyone who asks about rust! Have you thought of part 2 for things like lifetimes and the ecosystem (crates,cargo,docs,test)?
Thank you! That's a great idea!
As a top tier impatient I am very displeased that 49 seconds into the video you haven't yet moved to the main topic!
This video is amazing, the amount of information condensed in a little time is awesome and helps a lot to learn
Thank you so much! Make sure to read the source article I'm referencing, and do check out my previous 3 videos on the magic of Rust!
Very small correction : on most platform, long has 8 bytes, while int has 4 bytes in C and C++. Thus i32 refers to int or int32_t if you want to be really exact.
Other than that, excellent video.
> int has 4 bytes in C and C++
Also incorrect. int is defined to be at least 16-bit whereas long is defined to be at least 32-bit. So while int is indeed 4 bytes on a lot of platforms, the standard doesn't define it that way.
I could be wrong, but I don't think that's the case. In Java, you would be right, int is 4 bytes, long is 8 bytes.
In C/C++ though, long is 4 bytes, long long is 8 bytes, and int is determined by your architecture. If you're on a 32 bit computer, int is 32 bits aka 4 bytes. On a 64 bit computer, int is 64 bits aka 8 bytes. If you're somehow on a 8 bit computer, int is 8 bits aka 1 byte.
The architecture thing is also like isize/usize in Rust
@@zperk13 I don't think I can link anything here, but let me quote Wikipedia here:
> The minimum size for char is 8 bits, the minimum size for short and int is 16 bits, for long it is 32 bits and long long must contain at least 64 bits.
You can also find these in the actual C standard here: 5.2.4.2.1 Sizes of integer types
@@zperk13 yes, this is the case on many embedded systems. There are lots of things like memory alignment and specialized instructions that are system compiler specific and make these subtle things like data type sizes a bit complex. It all comes down to the computer architecture.
Wow I feel better for getting this wrong - what complexity! You folks seem like you might know the answer to this: Is i64 faster than i32 on typical desktop 64-bit system? Another commenter said this. If so, maybe I should recommend i64s?
3:16 Actually Javascript also has a block statement so the analogy with IIFE wasn't needed
Every day's a school day! Yes, another commenter pointed this out, that's great news. I already use `const`s exclusively in my js, it's wonderful to know they're even safer than I thought!
This video is not about Rust, the videogame... Oh well, I learnt stuff.
Surprise! I feel your pain the other way - it's very difficult to google for Rust language stuff without getting Rust game results XD
On my CPU (i7 930), 64 bit numbers are significantly faster than 32 bit numbers. Surprised me a bit
Oh wow! I mean... All modern cpus are 64 bit, might they be faster for all? BENCHMARKS NEEDED!
It depends, some machine code generated by MSVC (and others) for x86 regarding i64 operations is inefficient and improperly considers microcode implementations
@@mariocamspam72 Interesting! something for users of the `windows` crate, on legacy hardware!
you are not like the others who puts link filled with adds, so u deserve to be subscribed..... thanks for the plugin and all the best for future
Thank you very much for you kind words. I don't know if I will do ads in the future, something on-topic in the middle of the video that is relevant to my audience perhaps. I suspect I could do more videos if I was sponsored - but I also find ads annoying! I'd love to know your opinion here, and thank you again.
Play at 75% of normal speed. LOL -:/
This feels like c++ and python had a weird baby and then JavaScript adopted it. The strange mixes of syntax make me uncomfortable lmao
Let me set the record straight: It's LISP and Haskell sneaking into the popular kids party wearing C's coat.
Try out ruclips.net/video/4dvf6kM70qM/видео.html next and let me know what you think!
@@NoBoilerplate sorry, not raised by JavaScript, raised by wolves lol
Coming from the world of python, rust is an entirely different way of doing things but I kinda like it 😁
* cherry picking time *
python: uses self notation, self is passed as an argument
rust: uses self notation, self is passed as an argument
python: has Self type (3.11)
rust: has Self type
python: has lambdas
rust: has lambdas
python: has match statement (3.10)
rust: has match expression
python: has async-await
rust: has async-await
python: supports custom event loops (things that execute async), unlike JS
rust: supports custom event loops
python: built-in C interface (as CPython is the most popular Python implementation)
rust: built-in C interface
python: has context management ( __ exit __ )
rust: has context management (Drop)
python: supports b"bytes" syntax
rust: supports b"bytes" syntax
python: native support for AST modification (ast module)
rust: native support for AST modification (procedural macros)
python: has _
rust: has _
@@-parrrate counterpoints:
a) I have dabbled in other languages for fun/uni but only really properly know python
b) I barely know anything about rust (have never actually coded in it myself, only heard good things from friends) (but cool to know it has all those things too)
c) it's a throw away comment on a yt video, I don't have the time or will to research everything I say 100%
d) (not really a counterpoint) you mean nitpicking not cherry picking I think? Nitpicking is pointing out little flaws in something, cherry picking is deliberately excluding points that don't fit your arguement. (Tbf you can do both I guess but saying you're cherry picking a) doesn't fit and b) implicitly weakens your arguement)
@@-parrrate It's still very valid to say that Rust is a different way of thinking lmao. I've used Python and JS a fair bit and even with TS, I've still not had to worry about the particulars of `str` vs `String` or borrowing or ownership at all. There's a reason why the "higher level" languages are often used more by beginners.
Rust and python make good choices about many things. I've used python professionally for 15 years, but it's time to move on. The GIL is terrible for python's concurrency, and it benchmarks 80x slower than rust in single threaded tests.
Python's ast does runtime modification, macros are compile time modification - a very different beast.
I've been writing python professionally for 15 years, and I think it's time for me to move on.
Rust was just familiar enough for me to learn, but it took me a while. That's why I'm making these videos, do watch the others!
tuples were weird for me because python tuples are immutable but rust tuples are mutable, but man tuples are powerful, its like a struct but without needing to make one
What's your most valuable use case for tuples?
Python calls structs Named Tuples - I think naming the elements is way more useful. I don't use tuples very often, not for big work any way!
@@NoBoilerplate I think so, too.
Go relies a lot on Tuples since it doesn't have enums.
After thinking more about it, I mainly use tuples when wrapping a type (New Type pattern afaik)
I usually use tuples for returning more than 1 thing
@@CunningBard Yeah, a pair of things is often OK for a tuple. In Rust, I find I'd rather name it and call it a Struct so that I know what KIND of paired data I'm working with. Javascript has made me afraid of anonymous blobs of data
I thought as a Java/C#/F# dev Rust would be really difficult to pick up and rather uncomfortable, like C++, but its really not as big of a leap as I thought.
Same! I am from a python background, and though it was challenging, it was so worth it! :-)
I have been programming in different languages for 20 years+ and no language has ever made me fall in love again with creating software as much as Rust. If you code, you owe it to your heart and soul to check out Rust.
Thanks for the amazing content in this channel by the way!
"If you code, you owe it to your heart and soul to check out Rust" Can I quote you on that? :-)
Wow, man! You are really awesome. I am impatient to learn Rust, but now it's gone to see this video. I know python anD JS. It's pretty similar. But very advance. I need a suggestion. I want to learn a language that gives me the best performance and flexibility to do anything and keeps me on-demand in the job market. Is that the Language that I need ???
You have two very strong languages, JS and Python. Top #2 at the moment in terms of popularity!
redmonk.com/sogrady/2022/03/28/language-rankings-1-22/
I think learning Rust is a really good idea, it is already #19 in popularity, and I suspect already has a bright future too!
This video is truly awesome. Nowadays is very hard to find concise and good selected content about a language in only 10 minutes. We all know we won't learn the whole language in 10 minutes, but as someone who also just dives in the languages and takes its time to learn, this video cleared a lot of concepts about rust syntax (like reading and understanding the generics for functions and structs, or the '?' operator, or simply the '!' character that represents macros), it helps so much to understand what is written.
Thank you! Though all credit should go to Amos, I learned Rust from him! fasterthanli.me/articles/a-half-hour-to-learn-rust
Yo I thought this was a guide for the game rust. I’m like “woah, this is a really intricate guide” 😂😂
I have the reverse problem all the time!
3:04 - I wouldn't write "f -> void" if i were you. I'd use the proper type, "fn() or fn() -> ()" for consistency, and further explain that "() is a struct with no values. it is a unit struct, because it can only have one state; existing. it means void.".
Thank you! Errata pinned comment updated 👌
Your audio compressor is really annoying it's cutting off at least half of the first syllable every time you start speaking after a pause.
Rust is like the best parts of C++ and JS combined.
It's WAY more than that!
I tell people that Rust snuck the best parts of Lisp and Haskell, into the cool kids party in Lisp's clothing!
Was expecting a guide for how to build a base or raid an enemy's base...
Oh gods we both have the same problem! I can't Google anything about rust (the language) without turning up new player guides, build reccomedatuon and sniper scope mods. A delight!
4:23 well except for wildcard imports ``use std::*;`` and the prelude items (including importing crates, ``std`` is available despite not declaring ``extern crate std;``)
It's so simple yet so complicated, it's perfect lmao
Everything should be made as simple as possible, but no simpler. Most languages break this rule and pretend the world is simple!
I feel like i stumbled upon a cult
Welcome to the cargo cult! Let me know what you think of this follow-up video ruclips.net/video/oY0XwMOSzq4/видео.html
As a C++/C# dev, I was understanding it fairly well till you got to the error handling part. That’s gonna take me some time to understand fully.
3:09 technically it returns the unit type, i.e. ()
Oh yes! Thank you for the correction!
that sounds cool but where do I go to setup the IDE and how to I target the compiler to my rust program?
I'm glad you asked, my previous video in my Rust series answer this ruclips.net/video/ifaLk5v3W90/видео.html
Until now, I only had a casual interest in Rush, but your short introduction was exactly what I needed to become more interested. Well done!
Wonderful! I am delighted. Do watch my other videos (especially Rust is Boring) to get excited about WHY we are learning this complex language . The rust book is great too!
What the hell does “explicitly annotate the type mean”???????????
You’re speaking Spanish in Japanese………
Me as soon as the video starts: **Clicks on "Skip to Highlight"**
even better: Read the article I based this video on and skip around in real time with YOUR EYES!
fasterthanli.me/articles/a-half-hour-to-learn-rust
Great stuff to try and absorb whilst multitasking.
Jokes on you, my ADHD-ed ass couldn’t even last 2 minutes
I sympathise! I recommend my previous 3 videos which are full of Rust concepts, and lighter on code. The goal of them is to get you excited enough to pay attention to the boring bits (that's what worked for me!) Good luck!
There's low demand for rust right now but I hope there will be. The language and tooling is excellent! I find that one can significantly cut down cloud computing and upkeep costs if they switch to rust. It's good for the environment as well. AWS has started to support more rust so I think we'll find more demand for rust soon.
Absolutely! I said similar things in my previous videos!
Most of the Big Tech companies are in the Rust Foundation, so I would expect It to grow significantly over the next few years. WebAssembly may prove another sweet spot for high-perf applications in the browser client.
lightbulb moment when realising "macro" doesn't mean "constexpr"
Exactly! Game changer
This video is amazing, I wish there were more resources like this with programming
Owen! Thank you so much, you're so generous - but there IS another resource for rust: please do visit fasterthanli.me where the source of this video is taken from. Amos does SUCH great work on his site, he makes videos too, but his articles on Rust basically TAUGHT me the language!
Thank you again :-)
@@NoBoilerplate I absolutely will! This is a great resource for people picking up the language. It can be hard to do that initial read-through of the rust book without your eyes glazing over a bit when you don't have the full context about why certain features can be useful or if the language is right for you. Being able to get a super quick set of examples like this showing how rust code works and some of the features is incredibly helpful as a primer for the rust book.
@@theowenmccarthy Yeah! Agreed there, you saw my recommendations? ruclips.net/video/2hXNd6x9sZs/видео.html
@@NoBoilerplate Absolutely, I am following along! Thanks so much for your amazing explanations
I would be very interested to get your take on Vlang and Zig, two languages that seem to be vying for a similar space as Rust. All three are meant to be extremely performant by ditching a Garbage Collector, but similarly avoid the gaping pitfalls of manual memory management.
Of course, in most situations, it's not really accurate to say "X language is the best, objectively better than Y language."
I personally lack the experience to do a full breakdown of what each language offers to the developer, which projects benefit the most from each language's best features, and so on.
oh COOL! I'd not read up on Vlang. Looks like a great little low-level language inspired by Go. HOWEVER it has a GC, which means I can already tell many things about the language:
- No embedded development
- Can't write linux modules
- Imperfect for hard realtime applications (music, flight control software, ETL pipelines)
- No borrow checker superpowers
I wonder who this is for? A Go developer wanting lower-level code? Then why does it also have a GC? Hmm. Cute though!
Zig I love - huge huge fan. It really helps you manage memory in a sane way, and the whole language has no surprises. But the kicker is you still must do it, and you might forget. Zig is certainly a better C, but they didn't try to push the envelope.
Rust's lifetime annotations and borrow checker are a FEATURE, not a burden. A rich type system is great, but if you add lifetimes to the types, you've enriched them in ways that don't just mean the compiler can manage memory for you - you can build your own types with complex temporal logic in.
One day I'll do a video on this XD
@@NoBoilerplate *Interesting!* I'd come across some performance benchmarks where Vlang would actually beat out Rust, and I found no mention of a GC, so I just kind of assumed there wasn't one. Impressive for them to reach that kind of performance with a GC, even if it's not really swinging for the same ball park.
And I'd be very interested to see that video 😁
@@chrs-wltrs I admit I didn't get further than the front page, where they mention it! Apparently there's a new mechanism that can statically free 90% of memory cases, leaving the last 10% for GC.
While that is terrific, I am left wondering how much time they're going to invest in an imperfect solution XD
As for performance, Rust benchmarks in 1.1x C's speed (Java and JS are 4, Ruby is 20 and Python is 80). So while I can believe it, rust is fast enough!
This is almost C++17 in some strange syntax.
I really like the idea of Rust and want to learn it.
Coming from C++17 should be easy i thought.
( C++ from c++11 and up is just so easy to use and to use right )
But that is absolutely not the case.
And it is not because of the concepts of the language which i really like.
I get turned off almost immediately by the syntax and warnings about style.
( I use my own style :D )
Also it feels kinda restrictive.
That might just be because I do not yet know the language, but using C++
I feel like I can write just about everything.
With Rust its like hitting a wall every 40 minutes or something.
But still a good thing and I´m going to invest some more time into this.
Maybe some private Projects.
Cool! You're going to have a really fun time! My advice: Don't worry about syntax, every language has their own, and if you put 5 developers in a room, you'll get 10 recommendations for style! :-D
Here's my video on how to learn: ruclips.net/video/2hXNd6x9sZs/видео.html
Great video ! but we need a part 2 : lifetimes, differences between String and str and traits
Coming up!
Hmm...
From C++ to C# to DM to JS and TS, it's now time to learn rust. Surely I won't be bashing my head against a wall for the 5th time and I won't be trying to make a project that's way too complex for my skill level, right? Right?
Who am I kidding, it's bashin' time!
Good luck! :-D
My only question is what does the & prefix do in arguments and parameter types and when should I use it?
that means you're passing the argument by immutable reference. you should always do it if you don't want to change the value in place
Take a look at my previous video "Rust makes you feel like a Genius" for an explanation of the borrowing system. It's simple, but unfamiliar.
It means the function receives read-only access to the argument. It's called immutable reference. There's also &mut which takes write access. Without any prefix, the argument is taken by value, which means the function consumes it (unless the type is Copy, in which case a bitwise copy is passed in).
Bro I was looking for a game summary not a science class
Wow, I never thought Rust has a lot of functional programming language features. I'm interested now
Right! Do look at my previous 3 videos for more astonishing features you'd never have imagined!
why not .. seems like everyone one youtube wants to go back to the 1960"s
@@robbietorkelsonn8509 It's becoming clear that the Object Orientation experiment has not been a wild success. Note that Reactjs and those like it use a functional reactive paradigm!
Fun, slightly annoying “oh crap now I have to consider that while writing unsafe {} code” fact: If you have unwinding enabled (by default it is) you can actually catch a panic!() with std::panic::catch_unwind()!
Another thing to make sure you've handled in unsafe - thank you!
Very helpful content. I can’t even state how much I appreciate this format. Please make more high speed basics videos for rust. Or whatever. I’ll watch.
Thank you so much! I will. Video 11 (of this new format) arriving on Thursday. I may soon add another video, making my videos weekly, not on Rust, but on other interesting technical topics. Stay tuned!
Isn't it better to use an i64 than an i32 for most modern computers? Most of them are 64 bit.
better: isize
everyone is happy :D
To my knowledge i32/u32 is generally a better default since it's friendlier on the cache, despite having the same arithmetic performance.
Perfect intro. Just researching rust for a project and all other short videos are superficial or extremely long.
Keep up the good work up!
I've got 9 other videos on Rust just like this one, check them out!
Started software when big computer costing millions of us $ were having 512 Meg of memory...I am always say the same...You can learn a language in one week and you need 10 years to master it...there is NO shortcut and pain, hard work are the rule of the game.
Couldn't agree more, here's the way I teach Rust: ruclips.net/video/2hXNd6x9sZs/видео.html
This is amazing! Exactly what I wanted to see for an intro to the language.
Thank you! Do check out my other videos in my Rust series!
I was confused by 3:30, where the "tail" of the declaration block is: "y + z". To the uninitiated, this almost looks like a function without a return type, and in other languages I've not seen this type of compound assignment. It took a moment of staring to realize the tail isn't a void addition that can be read by itself, but has to be resolved in your head then "returned" to the first line.
It might have helped to put an example print statement or comment showing "x" is now "3". Cheers.
Good point! This pattern comes from functional languages, I believe. Lisp, elm, haskell etc
I'd heard of Rust, but didn't know what it was like. I didn't want to go through an hours long video describing every detail. I just wanted to get a sense of what it is like. This video gave me what I wanted. Thanks for doing the work.
My pleasure. This video focusses on the syntax specifically, which isn't quite the whole picture, check out other videos in my rust series, such as ruclips.net/video/4YU_r70yGjQ/видео.html
Operators that might be good to explain: & and !
Thank you for the suggestion, noted! The article I've based this video on is much better than the video fasterthanli.me/articles/a-half-hour-to-learn-rust
Great to see your channel growing so much in so little time (since you became talking about Rust)
Thank you so much! I'm having a great time writing these, and it's really helping solidify my own Rust knowledge (not least because when I make mistakes, people correct me!)
I think i'm gonna stay with c++, i don't wanna type so many "let" and "->"
I learned to love the syntax " data_type var_name = value"
This also remembers me of php and it's stupid dollar sign before any variable
Rust is extremely different isn't it! No inheritance, new syntax for lifetime annotations and borrows, and the compiler hates a lot of the standard normal patterns we've been using for decades.
I know how you feel. Back in 2020 I crashed out of learning Rust twice. First time due to multiple string types (Haskell's biggest mistake made again, I thought to myself) and second due to lifetimes. At the time I had a great mentor who picked me up and helped me back on the path. Most people don't have this. This is why I made my Rust series.
Yes Rust is very different from what you're used to. But that's the point. Two features you can't get in C++ that I think you'll like are Macros and the Unsafe system.
Macros are nothing like templates or cmptime (they're more like lisp macros), and the unsafe system is a genius way to ring-fence pointer arithmetic, to allow us to build safe abstractions around unsafe pointer code.
I did a video on both of them here, and I'd love your opinion on it: ruclips.net/video/PuMXWc0xrK0/видео.html
Cheers!
I started learning Rust and then sorta gave up and just picked it back up only after rewatching your previous videos on Rust for motivation, this was perfect, thanks!
My friend, this warms my heart. My EXACT REASON for making these videos is because Rust was so hard for me to learn. I crashed out a few times, and only was able to get through it because I had a mentor helping me through it. I am hoping people can re-watch my videos for a boost!
@@NoBoilerplate Your videos are short but highly technical, usually there is a trade off between length and technical depth. For me personally it provides that quick motivation from a shorter video and gets my curiosity going because of the depth. I had seen the impl keywords but didnt know what they did in that short span where you explained tham, I opened up a temrinal and messed around with the impls. Keep them coming! You're doing a fantastic job
@@frroossst4267 Well you're so kind, thank you!
can't I just run get_thing() and dont allocate anywhere? so instead of let _ = get_thing(), just: get_thing()
you can, but i think one might use
let _ = get_thing();
if get_thing() returns a result, to make the unused result warning go away.
personally, i use
get_thing().ok();
because it’s concise and it’s like saying “it’s ok” but that’s something i came up with on my own and might not be a good practice, especially since it’s conceptually doing an unnecessary operation.
I feel that rust is one of those languages where you need a knowledgeable mentor in the early days. I had a go at writing sha256sum in rust, and there was a lot of head-scratching and digging around to find out how to do things. Whereas in Python and C it was relatively straightforward. I say mentor because, when writing 'worked examples', you're guessing what the novice programmer wants to write. But rather, you need to start with a novice programmer who knows what they want to write, and then guide them as to how to write it in Rust.
You've got it exactly right. Back in 2020 I crashed out of learning Rust twice. First time due to multiple string types (haskell's biggest mistake made again, I thought to myself) and second due to lifetimes. At the time I had a great mentor (Shout-out to Alex!) who picked me up and helped me back on the path. Most people don't have this. They need the excitement of my hype videos to break through.
I will eventually run out of hype topics and move on to slightly more detail. But first, there's a few million developers I want to send to rustup.rs!
@@NoBoilerplate I've been learning rust recently, and chatgpt has been a great mentor. If I'm getting an error I can't make sense of, I can copy paste the offending piece of code and the error message, and like 80% of the time it tells me why it doesn't work. I still have to rely on traditional methods for the other 20%, but it greatly reduces the amount of head scratching I go through. It's been a bit of a challenge though, since nearly all of my experience is in C# and Python. I've never used a low level language before, so the learning the intricacies of low level + the intricacies of rust simultaneously has been challenging. I've come pretty far though!
@@sa1t938 oooh that's INTERESTING! I'm in deep with chatgpt, and I'm SUPER excited and scared for what 2023 is going to be like, with this tech revolutionising every single field!
I find writing C unbearable. Too low level, too much UB and too little abstraction facilities, unless you (ab)use the preprocessor. C++ is kind of OK but a real beast to tame...
Can somebody explain in a bit more detail what exactly the code at 2:34 is doing? Specifically, what is `slice.split_at(middle);` doing?
I might have invented that, though there is a doc.rust-lang.org/std/slice/struct.Split.html
I copied Amos's examples for the video here fasterthanli.me/articles/a-half-hour-to-learn-rust perhaps that particular line is psudocode?
How do you not have more subscribers?
You're too kind! But I'm not sure i deserve the ones I have! It's incredible!
@@NoBoilerplate between these videos and Lost Terminal, allow me to politely but strongly disagree, you deserve all these subscribers and more!
Humility is a great thing but don't down play your good work unnecessarily either 😊😊
@@NoBoilerplate
Well, you seem really quite skilled at condensing complicated topics down to understandable, short videos. The closest example I can think of would be Fireship or (, though it’s not on the same topic,) CGP Grey. For reference, they have 1,4M and 5,43M subscribers respectively.
Until you have at least a hundred thousand, I’d consider you underrated.
"i32 is equivalent to a long in C" this isn't really true. sizeof(long) under GNU/Linux returns 8 but 4 for windows.
Yep, a few people pointed out conflicting advice here - note the ERRATA pinned comment
You've actually got so quality stuff on your channel. Keep that up man!
Thanks, will do!
Come from JavaScript. Sigh didn't like typescript still need to learn about the type data and other things. Knowing to code correctly and understand take time to think correctly.
Typescript and Rust are the two most loved languages in the world (according to the stack overflow developer survey) and I think it's because they both are used by people who value correctness.
Check out my latest video in my Rust series on this ruclips.net/video/4dvf6kM70qM/видео.html
The Sequel: Tauri in Ten Minutes?
The native app framework? Maybe! Have you tried it?
@@NoBoilerplate Never tried it, but I plan to soon. It looks awesome. It's like Electron but using much lighter weight Rust for backend, glue logic, and a browser-like front end interface.
It claims to have the ability to glue other runtimes into the same binary, like Node.js, Julia, and Python, to mix and match polyglot tech stacks relatively easily.
I've been intermittently looking into whether I can use it to have Python & Pyscript do the front end UI stuff, with Rust in the back end to handle all the heavy data crunching and OS interactions, while sidestepping the staggering binary size & memory footprint bloat that comes with using chrome/electron. It seems possible.
As soon as I can make the time I really want to make a network mapping tool, because Visio is a crime against UX design, and it's looking more and more like Tauri would be the best way to do native application development.
This is being used in the Linux kernel now?! Ugh, this seems like a disaster waiting to happen - If you can't write a functional application in C or X86 Assembly then you should *NOT* be writing linux kernel drivers. At least it isn't full of Object-Oriented crap where developers tend to just write awful Java and give it a .cpp file extension.
Your faith in the intelligence of C developers is not shared by Microsoft, Google, or the OpenSSL team. They experience the growing pains of the language's flexibility:
Once your program becomes non-trivial, it appears to be impossible to avoid memory nightmares, which manifest as security holes so terrible that we give them names:
Slammer worm, WannaCry, Trident exploit, HeartBleed, Stagefrieght, Ghost
Rust is as strict as you wish other C developers were.
I'm not excited by rust because it's flashy, I'm excited by it because it's boring. Here's my video on this topic, I'd love your thoughts ruclips.net/video/oY0XwMOSzq4/видео.html
i was looking for this
thank you for making this video if possible please make a series of tutorial for rust for the people who already know some programming language
My pleasure! Read the original article too 😁
@@NoBoilerplate yes i will but i prefer video lectures over articles and documentation
I’ve only started learning to code about 5 months ago , of course with html and css and then JavaScript and I’ve mainly been focusing on JavaScript now , but watching this it seems hard maybe this video is fast too and as a beginner a bit over my head , some of it. But my question. Is , does anyone have recommendations on learning rust as a beginner ?
I sure do! Apart from the source of this video (check the description for the much better article I based it on), try:
- github.com/rust-lang/rustlings
- and read doc.rust-lang.org/stable/book/
Rustlings starts off REALLY slow, you'll be very comfortable. The book also is written very well, doesn't assume a software background. And do ask questions in #newbie-advice in the No Boilerplate discord, links on noboilerplate.org! Good luck!
I'm trying to create a programming language and I can't decide between using c++ or rust. I've tried doing some stuff in both, but it was a little difficult to do what I wanted with rust. No classes, can't assign references in structs without destroying the code with lifetimes and had many other problems while learning rust
Rust is certainly more difficult to learn, but it is WORTH IT! Have you watched my other videos on rust? In them I explain the unique features that you won't find anywhere else.
You're trying to create a programming language?
Yes, this is typical experience when starting to learn Rust, particularly for people coming from OOP. Rust is not the kind of language where you learn to translate syntax from language X, and you're good to go writing your code in whatever style you like. Rust has its own "coding paradigm", that's somewhere in between functional, OOP and imperative.
You tried to do some stuff in Rust, and it was difficult to do what you wanted, THE WAY YOU WANTED TO DO IT! That's the problem.
It took me about a year to learn the "Rust way of doing things". Unfortunately, I still can't fully explain what that is exactly. Especially not in a single youtube comment. People describe it as "becoming friends with the borrow checker", but never really describe how to get there.
@@NoBoilerplate Of course I did. That's why I decided to learn it :)
It is great because you can make no mistakes in your runtime because of rust if you use it the right way, it will have a difficult learning curve because of that, but like you say: it's worth it.
@@KohuGaly A year of learning is too extreme for me. I think I can learn it quicker, thanks to modern IDEs, but if it's worth in the long run, that's another question
I know im hitting this a bit late but do you have any Rust video course suggestions? I don't learn well by going through written books or general written content.
I certainly do, my recommendations on how to learn Rust are here: ruclips.net/video/2hXNd6x9sZs/видео.html
Though the Rust Book might not be for you, my recommendation of Rustlings will be - it's the best way to learn Rust!
On one hand, the compiler being this pedantic over almost all the things is fantastic since most "throw away code" is something you actually NEED to throw away and some crude prototyping can happen during compile time instead of runtime.
On the other hand, I think you can make some specialized logic based reprap that creates stubs and fake integrations before you move onto creating the "official integration" in some other language that maybe less concerned with some forms of errors that _may_ be caught in Rust before deployment. At least you won't have to deal with the type signatures made famous in that "American Psycho" business card parody of Rust functions from theSTEMgamer XD
Could you explain a little more?
If you can create a lambda calculus in Prolog, you can also create dependent types in this language.
maybe_fopen(_, _, -1, invalidFile(E)) :-
E = 'Could not open file'.
maybe_fopen(PATH, FLAGS, FD, RESULT) :-
((string(PATH), string(FLAGS)) ->
(integer(FD) ->
RESULT = validFile([PATH, FLAGS, FD]);
RESULT = invalidFopenReturn('File descriptor must be integer != -1'));
RESULT = invalidFopenArgs('Path and Flags must be strings')).
When you query for the result of this call like:
?- maybe_fopen("/tmp/foobar", 36, -1, R), print(R).
You now get ALL the possible ways this specific function call with these specific arguments can fail, including the -1 file descriptor AND the invalid argument types.
I'd say Prolog and similar constraint solvers in the logic programming space are one of the better tools for high level blueprint coding that can also be interactive since prolog can import and run these scripts inside of a REPL. This might be a great starter for automatically generated tests with functions/predicates in this kind of dependently typed domain, since it's cheaper to change the code up front at design time rather than review/production release time.
Jarble's transpiler on github and Warren's abstract prolog machine would be great study materials if you're more interested in the topic.
@@SimGunther That is very cool! Thank you
thought this was gonna be a rust (game) tutorial
fml I have the reverse problem when searching for tutorials for the rust language XD
I liked the idea of rust but have no experience with it
I loved when I used functional features like match case and expression instead of return in Scala
This video makes so much sense, thank you. I like Rust now, just need to convince the boss typescript isn't the answer to everything
Typescript is certainly 100x better than plain Javascript! But yes, ideally you'd get some rust in.
Have you seen my previous videos? The "perfect" and "genius" videos might persuade your boss :-)
Your boss is right, if you're working with web development
I thought I would come out knowing how to adapt the ak47's recoil, but I ended up watching a programming language tutorial.
Ha! I get it the other way around too - I keep getting rust game results when on Google for rust language stuff!
This is how tutorials should be; short, punchy, dense with useful information 💯
Thank you! All my videos are like this, here's another in the playlist if you've not seen it, I'd love to know what you think: ruclips.net/video/sbVxq7nNtgo/видео.html
I also like the short and dense format, although I felt there were places where the examples were confusing for beginners and a bit more explanation would have been very beneficial. For example, I wish the video had explained what |c| meant.
Anyone know what version of soft soft he's using? Like do I have to buy the $200 version for the stuff in the video or is the $100 dollar
What do you mean?
Rust could have featured a beautiful and concise syntax like C but they had to go mess everything up by adding clutter like 'fn' and reverse variable type declarations etc.!
For example: fn greet(name : String) { println!("Hi {0}!", name); } should simply have been: greet(string name) { printf("Hi %0!", name); } . It is the lack of straightforwardness and little details like this that makes rust a terrible mess! Every Rust example that I see I can convert into a much simpler and more beautiful and clutter free C like syntax! These new language developers simply do not care!
Style notwithstanding, there are features of Rust that do not exist in C. New syntax is needed to express these new features.
@@NoBoilerplate Of course there are new features and new paradigms in a new language like Rust but that does not mean you can't keep the language concise like C which is the golden standard of concise languages.
Bro, rust chose me, i might actually give it a try 😮
That's a very useful video, although, I didn't understand most of it, lmao. At least now I will go to the rust book and read it all, because what you showed is peeking my interest a lot
I'm so pleased! Have you seen my previous videos? They give an overview of rust. Definitely try the book!
@@NoBoilerplate Yes, I watched every of your Rust related videos and really enjoyed them, that is why I got recommended this video. Thanks so much for making them btw
9:28 what does |c| ? why just c.is_lowercase and c.to_uppercase() is not enough ?
|n| {n +1} is the anonymous function syntax in rust, same as ruby. The first part define the parameters, the second part is the function body. You'll see them a lot in In the iterator methods like map
This kind of presentation is too fast for me where I have to both listen to you talking and simulating the code in my head. Honestly I can't keep up
Ride the pause button, I believe in you! :-)
Coming from the C# world, just wanted to peak, this syntax looks so different :D
It is isn't it! That's mainly because of two big features that Rust has that C# (I believe) doesn't:
- Lifetime annotations (for modelling not just WHAT your data is but WHEN)
- References & borrowing. This is the secret sauce that allows you not just to not have a slow GC, but unlocks the Fearless Concurrency that Rust is famous for!
It's an investment, for sure. But take a look at a few other videos in my series, and you'll see magic that you can't get anywhere else!
Playlist here ruclips.net/video/Q3AhzHq8ogs/видео.html