ERRATA 3:51 I line 3 in the second code snippet is supposed to be `b = "newname"` (thanks VVill!) 1:02 Go is not object oriented, my mistake (I suppose I saw 'interfaces' and extrapolated from there) I'm delighted

“A fast executing language that crashes all the time is like a supercar… that crashes all the time” -0atman 2022

Alright that's it, I'm learning Rust. That's the first time I've ever felt happy reading a compiler error.

"Rust has an algebraic type system, and if you know what that is, you already know you want it in your language." no statement exists that is more perfect

To anyone starting out with rust: dont let the immature ecosystem scare you from using it . Unless you’re writing extremly critical enterprise software, the most popular library for the thing you want to do will have everything you will ever need

“A fast executing language that crashes all the time is like a supercar driven by Richard Hammond” -Jeremy Clarkson

I've heard that Henry Ford quote before. I would imagine people would've wanted a more accessible, available, cheaper and simpler horse, rather than a faster one.

Even if you do like dynamic language’s ability to just set something without specifying the type, Rust also lets you do that through type inference, which is pretty much having a cake (being able to define stuff without worrying much about specifics) and eating it too (it’s still static typing and you get all its benefits)

I've started my first project in Rust because of you! Thanks for spreading the word about Rust

Go cannot be a better c++, a language with a GC is fundementally solving different problems. Otherwise you could argue Java or c# is a better c++.

I used to be primarily a C programmer, a little bit of x86 ASM, and C++. I remember seeing videos like this and "C turned 50 today, so I decided to learn Rust" by Low Level Programming, and wondering what all the fuss was about. I eventually decided to give it a try, and it quickly became my favorite programming language. To me, it feels like what C++ should have always been. I know you made another video about this, but it really feels like in Rust I can focus on actually solving a problem instead of remembering to check for nullptr and use copy methods, all without introducing any runtime overhead. I write some code, cargo check, cargo build, then move on to the next problem. I don't need to study a method for an hour to make sure I didn't just implement RCE.

_"Rust might not be the language you wanted, but it might be the language you need"_ ~ Great Explanation

Thank you. Go, Rust, and Zig are not enemies. They are friends! Its interesting that you see Go as a replacment for C++. While it was designed as one, I tend to use Go where 10 years ago people would have used scripting languages: simple CLI apps, webservers, small tools. I also lean towards it for prototyping or 'throw-away' code, because the Go compiler's incredible speed makes iteration faster there. I use Rust where I need performance or safety and can afford to write from scratch. When I write Rust code, I'm confident that it's correct. In general, it's my preferred language for hobby projects. Rust also has best-in-class documentation, dependency management, and publication tooling. It's my personal favorite, so that's a tiebreaker. I don't use Zig (much, yet!), but when I do, it's where the pre-existing infrastructure expects C and C's conventions (i.e, in the world of device drivers, syscalls, and OS internals). Zig is still a bit immature, but the project is rapidly improving. Like it or not, the world we live in is built on 50 years of C, and not everything can or should be rewritten in Rust. Zig helps bridge that gap. The Zig community is incredibly generous w/ their time and expertise, too. They've helped both the Go & Rust projects, despite being significantly smaller.

Thank you so much for creating easy to understand, digestible and clear videos on Rust. Much respect.

Hi! There are 2 things in Rust that I personally like very much as well: First of all literally any compound statement is actually just another expression, returning the result from a final expression inside it when that subexpression is not followed by a semicolon. And even if it hasn't such an expression, it still returns a value, namely the Unit type, which is an empty tuple. There's no void return type. This is non-typical for C family programming languages, and comes from functional language influence. It's something that I really mis in C# for example, which is also a very great programming language by the way (I work with it for 20 years already). Second thing that I like is that Rust's object oriented way of programming chooses composition over inheritance strategies, which is good, because inheritance causes many problems.

I love this stuff. I'm retired, now, but I used C back in the day, close to the metal, for physics experiments. Before that it was assembler and sometimes machine code. But C does give you serious foot wounds on occasion. Rust has proper ideas to stop that while you still have real control over the runtime. (In my case, small computers/microcontrollers , networked, doing monitoring stuff). Great series, keep it up.

"Rust might not be the language you wanted but Rust might be the language you need" --Tris

I've always said, statically typed languages make reading code much easier, because I can be sure, that the things I see will always be that way. Dynamically typed languages make writing code much easier, because you can get things done without thinking too hard about the "what if's". Experience tells us that programmers spend much more time reading code, than writing code.

Rust community is very lucky to have people like you. Keep up the good work!

Wow. This guy’s talking so well about a compiled language that I feel he’s a script writer! So many statements that would be great chapter names ! Subscribed.

I'm a frontend dev, so basically as far away from C as a dev can get. But I've been looking into Rust for my bachelor thesis project, I was originally gonna use C++, (cause I need the kind of speed that makes JS just not an option) but the memories from first year classes are painful. I think you pushed me over the edge, so I am installing Rust today, and giving it a spin to see how I like it.

I think one major selling point with Rust is scalability within it's codebase. The Ruby team for example, chose to write the new JIT compiler (YJIT) in Rust because the code became too unreadable and complex.

Beautiful work here. I especially like that you put an unobtrusive progress bar on the video. Enthusiastically subscribed.

What do you mean Go is a better C++? Go has a Garbage collector. I would say Go is more of a better faster Python/Javscript thing, because it's still slower than C++.

As a python developer, typing every variable is very difficult work. But every line written in Rust, I think that it is very beautiful language. I love Rust and Rust love me.

Thanks again for another great and inspirational video, this platform needs more people with presentation skills like yours!

I am absolutely in love with Rust, and agree broadly on the thesis of this video, but having programmed in C most of my programming career, when you said "Is that all you want? A better C?" I almost dropped to my knees crying. It is all I want, I would love that very much

It is remarkable how consistent you sound across your different works of media (at least this and the Lost Terminal Broadcast). The voice, the patterns of speech, the precision of the expressions. Very recognizable. I like it.

I'll have you know, I'm reading through the Rust documentation and it's your voice in my head that I'm hearing. Good stuff.

4:37 - This is a _very_ useful way to think about the transfer of ownership, at least for us old dogs (who were rather mature programmers when C came out) learning new tricks.

Thanks for all of your rust videos. You've just came in time for me to choose a language for a new project. And I'm looking forward to use rust and become a part of rust community as well :)

Just now discovering more of your illuminating 10 minute videos. Usually I listen to coding vids at 1.5 or 1.75 speed...while doing something else. Not so with your stuff...I'm pausing, going back...yet at the same time, relaxing! Love your style, feels like you may have been a philosopher in a past or future lifetime 😶‍🌫

That cat joke was brutal.

Keep the good work up! Loving these.

I just like listening to you speak about rust. I haven't picked rust back up in months. I'm still sitting here with my typescript enjoying myself but whenever you post.... makes me wanna drop everything. Might be your soothing voice. Might be that you're talking about Rust. Hard to know.

I just found your videos a few days ago. Thank you very much. I look forward to your next video.

I think what would convince me more is some going through a significant project, Handmade Hero style, on UKposts, showing how they think through the code while they write it. I have a lot of little problems with Rust while I write it, sometimes the docs generated by cargo make my eyes bleed, and I don't really have a good IDE to help guide me through the syntax, so I would get more use out of a practical hands-on video at this point. If you have one to recommend I'd really like that.

Very nice, what I missed, the rust traits which allows to put features on existing and new types, for me a key feature, think about the iterator trait, once implemented for your type you can use all the iterator functionality implemented with rust. That is an extreme form of re-using code, …

9:30 if anyone else is confused, I looked it up and Rust has implicit returns, so the last line would be equivalent with `return Order(tris)`, which would leak memory outside the function scope.

your segment about lifetimes was great. and the order / account example really helps to understand it. would be great to hear more about ownership, borrow checker and lifetimes

There are also a new generation of proof oriented programming languages which bring another area to explore in the programming languages landscape: Coq, Lean, F*, Agda, Idris, ATS, HOL, Curry, Mercury.

Rust's syntax looks very scary to me as a beginner but I really want to start learning it, I don't know if rust is a good pick for a first language, I have some experience with programming but never decided to try and get into the nitty grittys of a language. your content is very inspiring and I hope you well, thanks for showing us rust!

Excellent video! Content structure, presentation and even the way it is narrated is very well done 👍 subscribed ✅

I would definitely follow a rust tutorial series from beginner to advanced that explains why we do things. Your voice is so calm:) Rn it is just watching tutorials, and then watch these videos for more in depth topics

I am starting to like Rust. I still want to build a project from start to finish it with, but from what I see so far it is pretty good. It is funny that concepts that I apply for C and C++ regarding memory management are enforced with Rust. And finally a compiler that is smart and tells you the error in a human-understandable way. I am a bit scared about integration with C libraries / C++ libraries, I hope I do not need to create wrappers and converters for it

Whatever was said about Java/JavaScript being 3-4x slower than C while Go being 2x is not true. In most benchmarks you will see C# /Java / Go very close to each other, with most edges being given to C#. The JavaScript part is correct.

Thanks for the videos about rust :) Rust is like accouting! You need it to run a smooth business, it is a hassel, but it is there for a reason. A rust program is like business unit, the programmer is responsible for following the "accounting rules" of the borrowchecker and the linter, no illigal transactions, no horsing around and if the "budget" of the program is correct, all is kosher! Rust + Rust analyzer is the coolest programming experience I've had, it almost feels like the code is writing itself (except when I fail to grasp what's going on, but then Shepmaster's answers on stackoverflow is always one google away) and I do love implementing strucks, enums and traits :) 🦀

Hey, I have been watching your videos on Rust and you make it much cooler. Love it keep up 💪

"Speed is a feature.." You're Goddamn right my man

“C has a templating system that is hot garbage“ 🤣🤣🤣 I love this video, how did I just stumble onto this channel today! Gotta join that Discord server

I'm just starting my Rust journey today after a few months kicking it back because of college. Awesome videos

I love how this videos background matches with the youtubes, making a nice blend.

C does not have a templating system. It has macros (as does also C++) which are, as you point out, a text substitution system. When you say about templates being "nightmare to use" it's partially true, but they have nothing to do with macros or just text substitution. I get you like Rust but there's no need to skew the facts to make it artificially look nicer. I think it's quite nice on it's own.

This guy is a rust ambassador, he creates FOMO in me. I am going to learn rust 😅💯

Currently going through The book - at chap 8th and am learning a ton, especially since im coming from Python and am not an experienced programmer. Great video!

Really really loved this video. I had stopped watching programming videos on UKposts for couple years now since all these channels have became repeating the same thing and also I don't like their general view on programming. I'm glad this one popped up on my recommendations. Coming from a JavaScript/TypeScript world, I've always wanted to take a look into Rust and see how it works and compares to its other related languages, now I actually I think I'm inspired to start from somewhere with your content and even start learning Rust.

I'm not entirely sure that the whole "reference vs value" problem of remembering which types follow which rules is fully gone: in Rust, you have to remember which types are Copy and which types are not. It's definitely not as big of a problem as remembering if something is a reference type or a value type (especially thanks to trait bounds) but it is worth noting.

"we have to know, through convention and experience "!! I've been saying this for years when teaching beginners about types. It's the reason I don't think it's wise to teach languages with runtime types to beginners.

8:16 as a random side note, Nim actually has a GC that works fairly well in (as far as my personal experience goes) at least a few embedded devices, e.g. the ESP32

The thing about Rust's ownership system is that it makes the *compiler* do what you would have to do anyway. Data ownership and lifetimes do not just go away and stop mattering because your compiler allows you to get it wrong. That's why Rust is so neat: For a newbie, the borrow checker provides training wheels that keep you from falling over, and once you internalize the rules of programming and gain expertise, it'll fade into the background but will still be there to catch you when your caffeine levels dip too low.

I'd heard about Rust before these videos, but actually started learning it after these came out, and now I'm rewriting old Python projects in Rust. On another note, I love the attention to detail here, and the fact that the errata comment even exists shows the quality of this channel!

Is it deliberate or accidental that the unsafe code snipped presented around 10:35 actually has undefined behavior? (Hint: Run it with “miri”, it’s available to install on nightly via rustup, or you can also find it in the playground under “Tools”.)

8:38 literally is a prophetic text from a God sent book

I have to say I love your videos they make me so happy. Thank you so much!

"Rust has an Algebraic Type System, and if you know what that is you already know you want it in your language" Somebody out there may know what it is and not want it, but I haven't met them.

10:00 C++ (not C) has templates but there are also constexpr, consteval & constinit that are just normal code and I think it's very unjust to not properly display such crucial points. Generally, your videos give a sense of prejudice sometimes, like you first think of what you want to say and then you try to somehow reason around your pre-determined opinion, ignoring everything that may invalidate the statement. I'm not saying you're purposely doing that, but sometimes your arguments feel very forced and it's a bit disappointing to have great explanations and essays mixed with this unnecessary litter. I, as a C/C++ enthusiast, believe in the power of Rust and I actually think it's great and in many ways better than other languages I know. I got inspired to really get into Rust (partially by you and I'm very grateful for that) and I've found it to be one of the best, if not the best, experience I've ever had with a new language. There's absolutely no reason to artificially present Rust as better when there's actually stuff to talk about and come to that conclusion. But please once in a while revise your scripts from the perspective of another language's user and think about how their view might be affected by unfair treatment towards their favorite "toy", which sometimes boils down to easily fixable things like poor research on fundamental concepts of languages (eg. Go isn't OO) or choice of words. I'm sorry for being so direct in this comment, but this is a thing that's annoyed me in many videos already and I hope you can incorporate my criticism into upcoming videos. I'm thrilled to see more from you, keep up the mostly good work and also I like your approach to error-correcting your videos, which I've found brilliant! No hard feelings

I am reading The Rust Programming Language. I like the guarantee of backward compatibility for the Rust compiler. I also like the features mentioned in the video (most of which are covered in the first six chapters of the book). I do not like the tiny type of the printed book which I have purchased. The lettering is too damn small, however the online version is very readable in my web browser.

0:23 When Jai eventually becomes public, I think it will take Zig's and Go's place, but for now, it might be Zig (For c), and Go (For c++).

I kinda want Rust's memory management in a Python interpreter. To me, that is the most compelling feature and the only major improvement that could be added to Python other than optional strict, static typing. (To simulate the latter, I use assert preconditions.)

Your lifetimes order_example() doesn’t compile. The tris Account variable has to be created outside that function. You can create it in main and then pass it into order_example but it won’t compile if it’s owned by that function.

I'm an ameteur programmer. I really only know java basics but have been looking for a language i can do basically anything i want with. Your vids have sold me on Rust, gonna make my Lightsaber as soon as i can.

Also, thank you so much for your hot take on C/C++ templates! I assumed I was 'not getting it', but I'm glad a way more experienced dev also thinks its weird :) Back in uni a whole course was about scientific meta programming in C++, and it was a complete mess...

I wouldn't call Go object oriented when comparing it to C++. It does OO very differently. While calling it OO is technically true, it kinda implies inheritance, which it very much does not have.

I had my Go pitchfork ready when you said it was object oriented! (saw ERRATA later) Jokes aside, great video once again!

Good videos as always!

8:07 In the game osu!, the GitHub issues page specifically has a bulletin for performance issues caused by the garbage collector-it's written in C#. Sometimes people experience lag spikes in the middle of gameplay because the GC just _decided_ to clean some stuff up, taking way longer than a frame to do so. Nasty stuff.

My cat comes when I call his name 😻, but even the vet thinks he acts more like a dog than a cat. 😅 Another great video.

How a developer starts interacting with rust. - Look at the code once, gets confused by a lot of unique features. - Start studying the book. Gets even more confused by all the technical details. - Start writing a few projects. Gets a lot of errors, start hating the language and all the time spent trying to making the compiler work. - Finish writing the project. Start testing and debugging. Realize it takes a few minutes to debug and test the ENTIRE project. - Finds out how fast the project runs. - Realize that all frameworks in rust are written in a similar way. No need to re-learn every time like in javascript. - Start loving Rust.

been learning rust for about 1 month now and I actually understand what is going on at 10:57 :). First watched this video about 2 weeks ago and I had no clue what any of that meant

1:48 "But a fast-executing language that crashes all the time, is like a supercar... that crashes all the time." Richard Hammond (and James May in "A Scandi Flick"): _nervous glancing_

not so sure about Go being a replacement for C++

I’m not sure about the rocket analogy. That implies C or C++ is on average slower than Rust. Which is definitely not the case. Instead, Rust is the car that doesn’t allow you to ride it if you plan on ever breaking road laws. Sure, the guy who isn’t bound by road laws will arrive at the destination 10% faster. But he also has a risk of dying in a car crash. The Rust car makes it impossible for you to get into an accident at a small speed cost.

Thank you for the video. I would be curious about a similar video about Crystal Language as it is pretty much an underdog right now.

“We have to know through convention and experience, that this duck will quack like a string”. Gold

6:23 In Python if you write name: str = 13, the program will run but any linter like Pylance will tell you that there is type mismatch. So you know what type variable should have.

0:40 No. I might agree, that Rust is not just a better C++ (honestly I think, it is), but Go is definitely not a better C++. Rust and C++ have these in common, which go doesn't: - generics (newest go has) - no GC - no reflection (runtime type information) - focus on zero cost abstractions - RAII - low level programming abilities (pointer math, etc.) Rust basically takes all the general ideas of C++ and implements them in a cleaner and safe way.

Also, Rust *does* have runtime - you almost always end up using tokio (or unfortunately less popular async-std). In addition, GC does *not* introduce indirection by itself. You can think of it as just another allocator implementation with tracing collection in places where it's impossible to directly infer where Rust-analog of .drop() is called.

The language I use depends on the environment and problem I am solving at the time. All languages have macros, it is just that the macro part is not built in : ) I regularly run code through a macro processor before running / compiling. I started running Pascal through gpm because at 300 baud it was far to verbose : ) For many problems you can define a model to solve the problem, a virtual machine to implement a programming language to solve the problem.

I don't see how Enums and Structs are a "weird" feature?

Every time I write Rust I feel like it's hugging me and saying "you can calm down now. You're safe. Things can be good, see?"

u r insane man !! Everytime u make a video about Rust, Something really excites to check it out !! Amazing RUSTACEAN u rr !!

You just convinced me to learn rust!

You are one of the most articulate, and sophisticated programming UKpostsr I have ever seen, subscribed!

I started hearing a lot about Rust recently, so I decided to read up about it before trying it. I decided not to use it and without mincing words, I just don't trust a language with that foundation list.

Good and accurate :) I am trying program in Rust for 5 years now :)

Love the blue line 😄

3:20 false, my cat does

Tried learning Rust. Got to lifetimes... almost had a stroke and gave up LOL

I love that lil crab.

At 8:00, wouldn't the garbage collector memory cleanup be done in a separate thread?