was skeptical when I saw the video was only 3 minutes, but this actually was an amazing overview. Thank you! Great analogy of the floor/workspace and packages.
Thanks! I was both skeptical and hopeful when I saw that 3 minutes video. It resumes it very clearly, although I had to watch it by small parts until it got into my head... Maybe15 minutes, back over and again.
I came across this channel while searching Actix example, and found great helpful. This video also feels brilliant to compare with actual packages. Thanks for the all efforts.
Thank you! Great explanation. Before the video I was wondering how you could have external modules without them having to be full-on binary packages themselves.
Thanks for the video, like the way you explain things.I still find the whole rust area in this messy. Ideally you dont want to refer to relative packages. the crate::etc never seems to work properly. So a workspace can only have one binary and many libraries? What if you wanted a core and have a web front end binary and a commandline front end. ideally you want them within the same workspace. Now, here is the kicker, if I have a library, i dont want to expose the code to someone else, I just want to give them a compiled libary and an interface file. similar to library files in java. only exposing what i really need to. Going beyond that, nobody really explains (in a cool way) the way you bring in a library and you can have full, prelude:* etc... meanings and use.
Workspace can have an arbitrary number of binaries and libraries. There's no such thing as relative packages, crate::etc is an absolute path to a module inside the same package. I don't think closed source distribution is something that cargo plans to support.
Sounds good, maybe check out the “build a Rust backend” video if you haven’t already - not 100% real world but it might be part of what you’re looking for!
@@codetothemoon sure it did helped me.. I have watched all of your videos, you have got really good content in here. But i am kinda requesting you to put backend api video with all of production ready service need to have like secure authentication, role management, database relation, scalalibility , maintainability etc.
Could you maybe talk a little bit faster? then the slightly older semesters would also have a chance to process your slow speech without falling asleep. Beside this: Good Video
yeah, the right pacing is hard to nail, and I didn't get it quite right in this vidoe. It's a bit of a tightrope. too slow and folks get board and click away, too fast and folks get lost and click away. I think I've gotten a bit better since making this one 😎
was skeptical when I saw the video was only 3 minutes, but this actually was an amazing overview. Thank you! Great analogy of the floor/workspace and packages.
Thanks Taylor! Glad you found it valuable!
Thanks! I was both skeptical and hopeful when I saw that 3 minutes video. It resumes it very clearly, although I had to watch it by small parts until it got into my head... Maybe15 minutes, back over and again.
I came across this channel while searching Actix example, and found great helpful. This video also feels brilliant to compare with actual packages. Thanks for the all efforts.
Happy you found your way to the channel, and thanks for the kind words! Glad you found the video valuable.
After wathing alot of videos, finally this one helped. Thanks so much.
nice, really happy you got something out of it! This one didn't get much traction!
Now this is a great explanation. Thank you so much for your compromise with Rust
Glad you found it valuable!!
Thank you! Great explanation. Before the video I was wondering how you could have external modules without them having to be full-on binary packages themselves.
You're welcome, glad you found it valuable!
Great explanation, thank you!
Glad it was helpful!
Had to watch a few times to understand, good thing it's only 3m😆
Hah yeah I tried to make this one as concise as possible, but might have sacrificed a bit of clarity in the process...
Amazing video, thank you very much.
thanks, glad you liked it!
Thanks for the video, like the way you explain things.I still find the whole rust area in this messy. Ideally you dont want to refer to relative packages. the crate::etc never seems to work properly. So a workspace can only have one binary and many libraries? What if you wanted a core and have a web front end binary and a commandline front end. ideally you want them within the same workspace. Now, here is the kicker, if I have a library, i dont want to expose the code to someone else, I just want to give them a compiled libary and an interface file. similar to library files in java. only exposing what i really need to. Going beyond that, nobody really explains (in a cool way) the way you bring in a library and you can have full, prelude:* etc... meanings and use.
Workspace can have an arbitrary number of binaries and libraries.
There's no such thing as relative packages, crate::etc is an absolute path to a module inside the same package.
I don't think closed source distribution is something that cargo plans to support.
Please upload real world backed api in rust.
Sounds good, maybe check out the “build a Rust backend” video if you haven’t already - not 100% real world but it might be part of what you’re looking for!
@@codetothemoon sure it did helped me..
I have watched all of your videos, you have got really good content in here.
But i am kinda requesting you to put backend api video with all of production ready service need to have like secure authentication, role management, database relation, scalalibility , maintainability etc.
@@pathakvivek7865 got it, thanks for the feedback! I’ll put those topics on the roadmap.
Could you maybe talk a little bit faster? then the slightly older semesters would also have a chance to process your slow speech without falling asleep. Beside this: Good Video
yeah, the right pacing is hard to nail, and I didn't get it quite right in this vidoe. It's a bit of a tightrope. too slow and folks get board and click away, too fast and folks get lost and click away. I think I've gotten a bit better since making this one 😎
":" is your friend. (";" if it's too fast)