I'm only finding this video three years later but I just have to echo this. I've always struggled explaining stack/heap to people and this analogy makes it so super simple. I'm totally stealing this. 😀
I can see you haven't made any videos in a while. Please don't give up, your doing great. I know TH-cam channel growth can be slow, but you will get there at some point. Love the videos, keep up the great work.
Please continue making videos, you're clearly one of the funniest and best channels about programming ever ! I'd even say that if one day Rust becomes more popular, your channel could become very successful ! I really enjoy your Rust videos, I hope more are coming soon.
Every TH-cam video about Rust is always at least half an hour long and I've put off learning just because of that, but finally I've found something good
I came across your video while trying to figure out why I got errors no matter where I tried to put an '&'. At the end of the video, I looked at my code, went "huh," and typed a single '&' next to one of my variable calls. Immediately every red squiggly line disappeared. Thank you! You explained ownership in an extremely helpful way.
Hi, at 4:11 you made an example which does not allow a copy of x to a because of rule 2. So far I understand this. Could you please explain why a copy would be ok if we would assign the following: let x = "Hello World"; let a = x; println!("{},{}", a, b); So there must be a difference between let x = "Hello World" and let x = String::from("Hello World"). I heared something about string literal and string type but I do no really get the difference. Is "Hello World" stored at the stack? Thanks
When it becomes invalid, its value is still "hello", but isn't anymore after it became invalid. If you try to access it, it will throw an error (The compiler will throw an error because it's intelligent).
I had to laugh so hard after seeing the angry face at 2:00 I have very little sleep, but this made me laugh hard. Thank you for making me laugh and thank you for the explanation.
ive never programmed in rust before, but why shouldnt we be able to have two pointers pointing to the same address? Like if I just wanted to iterate over an array or linkedlist I would probably need many variables pointing to the same location
You are great, what do you think is the best way to represent a Cyclic Graph with multiedges in-memory store and enable parallel reads/writes concurrently to the graph? .. am coming from erlang/elixir world where the shared memory is a sin, but I could use ets(memory erlang term storage) and let the genservers/processors(independent heap) get copies from the ets , now my question, how borrowing feature is diffrenent? Is the data is copy as well like elixir? Do you recommend me to move to rust instead of elixir ? Is it possible to have more parallelism in rust more than elixir? I think parallelism algorithm highly depend on shared memory approach? Elixir and rust seem they share a lot, thank you for this amazing work
I love Elixir as well! They solve different problems. If you need something really fast where you can have a very good understanding of the nuts and bolts, I'd choose Rust. Elixir has a larger ecosystem (due to the Erlang ecosystem interop as well) and feels quicker to build distributed systems in. The real question is, why not both? There's a library called `Rustler` that lets you call Rust from elixir. This might be useful if you have a small piece you need to make performant. Finally check out this conference talk. It's an actor library written in Rust, and demonstrates some incredible features. "Type Safe & High Perf distributed actor systems with Rust" - th-cam.com/video/qr9GTTST_Dk/w-d-xo.html Thanks for the comment! =D
Thank you a lot for your quick response, i actually was thinking of enabling both to work together where rust work as engine for the graph and receive requests from genservers(elixir)(handling concurrent connections) this way I will take the best from the two languages. thanks again for this amazing content, pls keep up the good work. All the best, am going to watch the link ;)
hey this looks like the programming language i was thinking of one day making. except i dont understand why they changed the syntax, whats with all that ! ! stuff and why does it become read only when borrowed. i dont get that
my only suggestion is slower pace. Watching your videos on normal speed is like watching other coding videos at x2 speed. If someone wants it faster they can always up the speed at normal quality, but trying to down the speed to 0.75 is weird and sounds choppy thanks to however youtube is encoding the speed change.
You have done an amazing job so far. I wish your videos had subtitles but I know it's so hard. Maybe speaking a little bit slower it's a tip too, since I am not a native english speaker. That said, this channel is great! Keep it up!
hmm, but why does this code work then: let i = "ds"; let mut ii = i; ii = "yoyoyoy"; println!("{}", i) this prints "da", which indicates that the value was copied. But judging from your explanation this shouldnt even compile
str literals are immutable and copy. `ii` ends up a copy of `i`, and there is no ownership to memory on the heap. However String points to memory on the heap and doesn't implement Copy, which then causes the compilation issue. Example: play.rust-lang.org/?gist=9ae38ace6a310ca4c2d55077d77635e4
That was one of the greatest analogies for teaching scope I have ever seen. Also, thank you for helping me understand rust's ownership!
Cheers! Glad the video was useful :)
I'm only finding this video three years later but I just have to echo this. I've always struggled explaining stack/heap to people and this analogy makes it so super simple. I'm totally stealing this. 😀
This channel deserves A LOT more subscribers!
Holly crap, this video is golden
You're an amazing person!
Thank you, dito.
I can see you haven't made any videos in a while. Please don't give up, your doing great. I know TH-cam channel growth can be slow, but you will get there at some point. Love the videos, keep up the great work.
no u
Did you just comment this to your own video? :) haha you must feel amazing about your own personality :D
This is the best borrow system explanation yet!
Please continue making videos, you're clearly one of the funniest and best channels about programming ever ! I'd even say that if one day Rust becomes more popular, your channel could become very successful ! I really enjoy your Rust videos, I hope more are coming soon.
One of the best programming tutorials I've ever seen. Thanks!
I just started with Rust and this video was super helpful! Keep up the excellent work, you deserve way more subs!
mind blow. of how easy you make complicated rusty concepts look. keep rocking dude
I just finished reading the Ownership chapter of the book and this further solidified and clarified the lessons, thank you!
this is the best programming channel I have discorvered! subbed.
Every TH-cam video about Rust is always at least half an hour long and I've put off learning just because of that, but finally I've found something good
I wish to have similar videos covering the entirety of rust? your videos are vivid and make it easy to understand Rust for a programmer
This is the best way I've seen ownership being explained. Thank you!
What a gem of a channel 💎
I am having so much fun learning #Rust. Thankyou you guys @YouCodeThings, these videos makes it so effortless. Thats the power of community
ACTUALLY SUCH A GOOD VIDEO i like the animations and explanations just makes it that much easier from going from something i know to jibberish code
Really enjoying the color scheme of this channel ☺️
I came across your video while trying to figure out why I got errors no matter where I tried to put an '&'. At the end of the video, I looked at my code, went "huh," and typed a single '&' next to one of my variable calls. Immediately every red squiggly line disappeared. Thank you! You explained ownership in an extremely helpful way.
that a wonderful explanation, so much time invested in making the difficult concept clear by animation.
Really loved this video, especially the out-of-scope lesson
Really didn't get into my head just by reading the book, this was super useful!
This video is great. Love the call stack analogy.
this is the best explanation i have ever seen, subbed
oh yea also you dropped this : 👑
The Friendly way to Learn Rust , and i love it . Thanks mate
this channel deserves many more subscribers.
subscribing to your channel is the best thing that happen to me. loved your tutorials.
Thanks for leaving a comment and subscribing!!! :) Your comment is the best thing that's happened to me.
Was just reading chp.4 in the Rust book and this really helped
WHOA! This is super clear and well explained. 🤯
Ownership animation amazing thx fully
Thanks for such a clear explanation. The animations really helped, lol. Thank you YouCodeThings
Nice style making video. Very fun!
Hi,
at 4:11 you made an example which does not allow a copy of x to a because of rule 2. So far I understand this. Could you please explain why a copy would be ok if we would assign the following:
let x = "Hello World";
let a = x;
println!("{},{}", a, b);
So there must be a difference between let x = "Hello World" and let x = String::from("Hello World").
I heared something about string literal and string type but I do no really get the difference.
Is "Hello World" stored at the stack?
Thanks
This is such great content. Thank you!
Great video. Too much work into each video. I like it.
Thank you! I got way too into those animations in this video!
This explanation was amazing!
You are a great teacher. Glad I found your channel..
This is hella professional, great work.
Oh! (...) my! (...) God! That is gooold! Thanks so much! Cheers from Brazil!
I like your videos and its style! Thanks!
you really teach in very nice manner, instant subscribe
4:42 when the variable X becomes invalid, what exactly then it equals to? what will be the value of X when it comes invalid?
When it becomes invalid, its value is still "hello", but isn't anymore after it became invalid. If you try to access it, it will throw an error (The compiler will throw an error because it's intelligent).
7:18 wouldn't &a[0..2] return hel? same for the second one, it's one letter too long
Damn, didn't understand this up until now. After watching the video, it kind of clicked and I actually understood! Thanks :D
Really great explanation, thank you!
I love your video😂 it was great and interesting! Please continue your style
I had to laugh so hard after seeing the angry face at 2:00
I have very little sleep, but this made me laugh hard. Thank you for making me laugh and thank you for the explanation.
Ownership explained clearly ❤️❤️
Hey can you share the idea of creating this video like in the 2d drawing with the animation, what softwaresthat you had used?
ive never programmed in rust before, but why shouldnt we be able to have two pointers pointing to the same address? Like if I just wanted to iterate over an array or linkedlist I would probably need many variables pointing to the same location
Your channel is amazing ! Keep up the good work :)
Excellent explanation ! Thank you very much.
Dude your videos are super good, keep going and thank you :)
thanks so much, I was wondering why the & was used sometimes but now I get it!
This video is more explained than the Rust Book.
These are entertaining and informative - thank you
Great thanks! Excellent stuff.
Wow, this explanation is awesome!)🦀❤
Good descriptive video, simple and concise, thank you!
Super cool video! Subscribed!
Love your vids!
Wow this is well explained and really consice and clear. Very good job.
the best video on ownership amaizng
Best video ever
You are great, what do you think is the best way to represent a Cyclic Graph with multiedges in-memory store and enable parallel reads/writes concurrently to the graph? .. am coming from erlang/elixir world where the shared memory is a sin, but I could use ets(memory erlang term storage) and let the genservers/processors(independent heap) get copies from the ets , now my question, how borrowing feature is diffrenent? Is the data is copy as well like elixir? Do you recommend me to move to rust instead of elixir ? Is it possible to have more parallelism in rust more than elixir? I think parallelism algorithm highly depend on shared memory approach? Elixir and rust seem they share a lot, thank you for this amazing work
I love Elixir as well! They solve different problems. If you need something really fast where you can have a very good understanding of the nuts and bolts, I'd choose Rust.
Elixir has a larger ecosystem (due to the Erlang ecosystem interop as well) and feels quicker to build distributed systems in.
The real question is, why not both?
There's a library called `Rustler` that lets you call Rust from elixir. This might be useful if you have a small piece you need to make performant.
Finally check out this conference talk. It's an actor library written in Rust, and demonstrates some incredible features.
"Type Safe & High Perf distributed actor systems with Rust" - th-cam.com/video/qr9GTTST_Dk/w-d-xo.html
Thanks for the comment! =D
Thank you a lot for your quick response, i actually was thinking of enabling both to work together where rust work as engine for the graph and receive requests from genservers(elixir)(handling concurrent connections) this way I will take the best from the two languages. thanks again for this amazing content, pls keep up the good work. All the best, am going to watch the link ;)
Just what I needed. Great job!
hey this looks like the programming language i was thinking of one day making. except i dont understand why they changed the syntax, whats with all that ! ! stuff and why does it become read only when borrowed. i dont get that
Well explained, hats off
Very well explained! Thank you so much :D
You're welcome!
you forgot to mention that this only for reference types not value types
Explained really well!
Thankyou for this clear explanation :)
Great video! Thank you so much!
Is the idea of the heap the same as c++? That is, the heap is extra memory the program requests from the OS while the program is running?
Yep!
Realy good explanation!!!
this is brilliant
Hey man! good job, keep it up
Thanks for teaching Rust!
This video is so fucking great.
Thx for great explanation!
Maaan, you should make more learning videos. It's damn funny and useful.
Good work :)
Hey @youcodethings Great content 👍, please do more videos , if possible regularly!
Tell me, what can I do to become the best coding channel for you?
Give us more! :D
give us examples of that is rust was created for - safe async/parallel programming.
Make a playlist of this!
my only suggestion is slower pace. Watching your videos on normal speed is like watching other coding videos at x2 speed. If someone wants it faster they can always up the speed at normal quality, but trying to down the speed to 0.75 is weird and sounds choppy thanks to however youtube is encoding the speed change.
You have done an amazing job so far. I wish your videos had subtitles but I know it's so hard. Maybe speaking a little bit slower it's a tip too, since I am not a native english speaker. That said, this channel is great! Keep it up!
What microphone do you use? You have spectacularly good audio quality.
I feel you sound like Dr. Seuss: there is a nice rhythm to the way you talk.
SICK VIDEO!
Good explanation
nice explanation, thank you :)
Nice video!
Why aren't you making new videos...your videos are great.
Appreciate it! A lot going on. Currently working on some larger game projects. Want to eventually make some videos on that process.
Love it.
amazing. thank you.
No, ur an amazing person *inserts keanu.jpg*
*blushes* Oh you
&mut str is not possible as &str is immutable
Holy shit. I understood this.
hmm, but why does this code work then:
let i = "ds";
let mut ii = i;
ii = "yoyoyoy";
println!("{}", i)
this prints "da", which indicates that the value was copied. But judging from your explanation this shouldnt even compile
str literals are immutable and copy. `ii` ends up a copy of `i`, and there is no ownership to memory on the heap.
However String points to memory on the heap and doesn't implement Copy, which then causes the compilation issue.
Example: play.rust-lang.org/?gist=9ae38ace6a310ca4c2d55077d77635e4
Thank you! ^.^
Thank you for the suggestion!!! :)
i FINALLY learned pointers
Yay!
good vid ty - new sub
Why do I still find this confusing? D:
You got this!