i applaud you compiling it first, getting an error, and then correcting it second. this way the learning comes naturally as it is done step by step. rust compiler is fantastic, so friendly to use.
Recently I was really confuse about modules and the use statement, even tho I'm an experienced programmer in other languages, and you made the best tutorial on this, 7 minutes and modules in Rust are crystal clear for me, thank you very much!
You have an excellent teaching technique, go straight to the point, I wish you could make more videos, your explanation is among the best quality up there, can you consider making a full Rust-project tutorial (maybe something easy for us to follow like creating CLI or something). Anyway, thank you again for your excellent tutorial. you've resolved the modules in Rust for me for sure.
Very nice tutorial, it is concise and covers the scenario when the module becomes bigger. You save me time from going through the document. Thank you. Quick question, is it required to have the module file name as mod.rs ?
Thanks for the video! Organizing Rust modules might be tricky sometimes. May I ask what terminal are you using? It catched my attention the way you moved the split at the right bottom with your mouse.
Your welcome :) I'm actually just using the gnome-terminal in this video. But I think you're referring to the window manager I use because that's what allows me to move and resize my terminal with my mouse. In this video I'm using the dwm window manager
Really nice way to explain this concept, my only take is the screen a bit cluttered, probably it will be confusing to a non-Linux WM user. Thanks a lot.
Nice tutorial. Couple of pointers. As you are wizzing around (vim/neovim) it is so hard to see the directory structure of the project. This is more important on the last bit (which is probably more important as you scale up). Would have been good if some more time was spend showing multiple files/modules and modules from other creates of your own library, referencing and using them.
thanks so much! i was really confused why i see both `mod` and `use` at the top of rust files. but now i understand. we have `mod` to bring modules to scope and we have `use` to grab things from module that we will frequently use.
New video from Jeff???? Whoa mama! Hummina hummina hummina bazooooooooing! *eyes pop out* AROOOOOOOOGA! *jaw drops tongue rolls out* WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF *tongue bursts out of the outh uncontrollably leaking face and everything in reach* WURBLWUBRLBWURblrwurblwurlbrwubrlwburlwbruwrlblwublr *tiny cupid shoots an arrow through heart* Ahhhhhhhhhhh me lady... *heart in the shape of a heart starts beating so hard you can see it through shirt* ba-bum ba-bum ba-bum ba-bum ba-bum *milk truck crashes into a bakery store in the background spiling white liquid and dough on the streets* BABY WANTS TO FUCK *inhales from the gas tank* honka honka honka honka *masturabtes furiously* ohhhh my gooooodd~
Thanks for the video. For future videos, when you're trying to teach people about how to setup the rust directory structure, maybe don't use some file explorer most of us have never seen before. What the hell is that? Nano? I spent all my time trying to figure out how it was representing files and folders on your screen, rather than focusing on what was actually being created. It's great that you know how to use nano to create folders and files without closing it. Use that all you want. Just don't do it in a demo that's completely unrelated to nano. You're taking the focus away from what you're trying to teach.
Thanks for the feedback. I used it because it gave a nice folder preview to show the contents of a folder without me continuously go in and out of folders. I'll try to find something more graphical in the future so its easier to follow along
@@Kamiyaa That's kind of the problem. It doesn't matter how nice an interface something has. It only matters how familiar people are with it. There was an experiment years ago, when computers were just being developed, where people were given a computer mouse with no explanation of how it works, and no one could figure it out. Even the things we think of as inherently intuitive are only intuitive because we are familiar with them. If you want people not to focus on what file explorer you are using, but rather what you're actually showing them, don't "find something more graphical". Just use regular bash. No themes. No plugins. Regular bash. Everyone knows bash. You could also use a GUI file explorer like nautilus (or whatever they call it these days). Everyone is familiar with that as well.
![[✨МОДУЛИ] Разбираем модули в Rust, разбиваем код программы по файлам 😎](http://i.ytimg.com/vi/RbYCyJx2bXA/mqdefault.jpg)
You probably don't know, but you're a hero. Really simple, well organized and clean tutorial. Thanks a lot for your work!
i applaud you compiling it first, getting an error, and then correcting it second.
this way the learning comes naturally as it is done step by step.
rust compiler is fantastic, so friendly to use.
Recently I was really confuse about modules and the use statement, even tho I'm an experienced programmer in other languages, and you made the best tutorial on this, 7 minutes and modules in Rust are crystal clear for me, thank you very much!
Appreciate the short tutorial. Love how it's short and straightforward.
Great concise tutorial! I'm learning rust with the rust book and I think your videos will help a lot to make me understand things better
Bestest explanation!
Simple and concise, thanks
You have an excellent teaching technique, go straight to the point, I wish you could make more videos, your explanation is among the best quality up there, can you consider making a full Rust-project tutorial (maybe something easy for us to follow like creating CLI or something). Anyway, thank you again for your excellent tutorial. you've resolved the modules in Rust for me for sure.
Awesome tutorial
Wonderful! Simple and clean!! Keep it up!
This video was so well done easy and clear. thank you so much!
Fantastic tutorial. Thank you for spending the time making it.
so, the module is like a namespace in c++?
Very nice tutorial, it is concise and covers the scenario when the module becomes bigger. You save me time from going through the document. Thank you. Quick question, is it required to have the module file name as mod.rs ?
Yep, it has to be mod.rs!
This was super duper helpful.
Nice tutorial, Thanks for making this.
Perfect... The simplest vid
Thanks for the video! Organizing Rust modules might be tricky sometimes. May I ask what terminal are you using? It catched my attention the way you moved the split at the right bottom with your mouse.
Your welcome :)
I'm actually just using the gnome-terminal in this video. But I think you're referring to the window manager I use because that's what allows me to move and resize my terminal with my mouse. In this video I'm using the dwm window manager
Wait you can extend nano?
Really nice way to explain this concept, my only take is the screen a bit cluttered, probably it will be confusing to a non-Linux WM user. Thanks a lot.
It isn't that complicated lol finally understood it thx
Nice tutorial. Couple of pointers. As you are wizzing around (vim/neovim) it is so hard to see the directory structure of the project. This is more important on the last bit (which is probably more important as you scale up). Would have been good if some more time was spend showing multiple files/modules and modules from other creates of your own library, referencing and using them.
Thank you so much for this tutorial. This made no sense to me until now
Thank you for this tutorial !
well done Jeff
thanks so much!
i was really confused why i see both `mod` and `use` at the top of rust files.
but now i understand.
we have `mod` to bring modules to scope and we have `use` to grab things from module that we will frequently use.
THANKSSS!!!!!!!!!
I am probably not the first one to mention this but are you really using nano? On your projects? Kind of based
I find it has a minimal UI ideal for tutorials :)
@@Kamiyaa fair
Mind if I ask what operating system your using? Keep up the good work :)
I'm using Gentoo Linux :)
what is this editor? it looks cool, is it emacs?
Its micro :) github.com/zyedidia/micro
@@Kamiyaa Thanks!
New video from Jeff???? Whoa mama! Hummina hummina hummina bazooooooooing! *eyes pop out* AROOOOOOOOGA! *jaw drops tongue rolls out* WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF WOOF *tongue bursts out of the outh uncontrollably leaking face and everything in reach* WURBLWUBRLBWURblrwurblwurlbrwubrlwburlwbruwrlblwublr *tiny cupid shoots an arrow through heart* Ahhhhhhhhhhh me lady... *heart in the shape of a heart starts beating so hard you can see it through shirt* ba-bum ba-bum ba-bum ba-bum ba-bum *milk truck crashes into a bakery store in the background spiling white liquid and dough on the streets* BABY WANTS TO FUCK *inhales from the gas tank* honka honka honka honka *masturabtes furiously* ohhhh my gooooodd~
what is the outro music?
Thanks a lot
thx shana
If there's one thing I hate about Rust, it's the module system. It was so much simpler in C#.
Should have run the `tree` command at the end of the video
Thanks for the video. For future videos, when you're trying to teach people about how to setup the rust directory structure, maybe don't use some file explorer most of us have never seen before. What the hell is that? Nano? I spent all my time trying to figure out how it was representing files and folders on your screen, rather than focusing on what was actually being created. It's great that you know how to use nano to create folders and files without closing it. Use that all you want. Just don't do it in a demo that's completely unrelated to nano. You're taking the focus away from what you're trying to teach.
Thanks for the feedback. I used it because it gave a nice folder preview to show the contents of a folder without me continuously go in and out of folders. I'll try to find something more graphical in the future so its easier to follow along
@@Kamiyaa That's kind of the problem. It doesn't matter how nice an interface something has. It only matters how familiar people are with it. There was an experiment years ago, when computers were just being developed, where people were given a computer mouse with no explanation of how it works, and no one could figure it out. Even the things we think of as inherently intuitive are only intuitive because we are familiar with them. If you want people not to focus on what file explorer you are using, but rather what you're actually showing them, don't "find something more graphical". Just use regular bash. No themes. No plugins. Regular bash. Everyone knows bash. You could also use a GUI file explorer like nautilus (or whatever they call it these days). Everyone is familiar with that as well.
@@talz8397 yea that works
0 Value.