Great stuff, well presented. Just a note: Arc = "Atomically Reference Counted". Which is safe across threads as opposed to Rc which reference counted but not safe across threads.
Great content and explanations! There were typos and discrepancies in the code that made for good challenges while trying to follow along (relatively new to Rust here), would have benefitted from having a link to the finished code
Couple of notes: - This video is LOONNGGGG (but that's ok, it's informative) - Typo in the slide at 7:44, where /n should be , but in fact it should be as per RFC2616-2.2 - At 12:25 the parameter in the function argument is `path`, while you pass in `resource` to node.get - the `let res = Response::new(client);` needs to be mutable (?) (before and up to 18:55) - At 19:31 (unless i missed something) you never handled the else clause for handle/Some(handler) which would(should) check for a static file or return the 404 page Side note: I skimmed over the forking/threading, since I already had that in place from another tutorial, I would say that I would avoid using libc::fork, since now you broke cross os compatibility, pretty sure fork doesn't exist on windows. and the usages of unsafe are can be avoided if you're just spawning threads from the threadpool. (unless there is some huge advantage over forking that I don't see?) Other than that, I'm amazed how the quality of your videos increased significantly in only a few weeks! I really do love this presentation style that you've developed, it's very easy to follow. Keep up the good work! One request, since I can't find any good tutorial/documentation about it, if you know how; I would like to know how to implement a custom `#get("/")` (for example) macro that eg, rocket uses for the routes.rs mod. If you could cover that in a future video, that'd be amazing.
I like the more advanced topics, but I didn't quite understand what was happening in the reader/line reader part around the 12 minute mark. I understand it's to prevent an attack vector around user not sending newlines, but a diagram would have been helpful to show how "reader.fill_buf" works
Nice presentation but the title is a bit misleading. Expected to learn something about async (futures, await, etc...) but there's only info about parallelism based on OS threads.
That's too complex for me. For someone who has just started with rust, I feel it's going to be long and tough journey. Just a suggestion, could you also make some short tutorial series for Rust and side by side cover such advance topics..
Great stuff, well presented. Just a note: Arc = "Atomically Reference Counted". Which is safe across threads as opposed to Rc which reference counted but not safe across threads.
Excellent content, thank you! Not many videos that go into the interesting details of this
Fantastic man , TH-cam so long to recommend me this channel, amazing content to learn Rust, Thanks a ton!!
very nice presentation and great content! How do you "play" your edits/diffs so that they "morph" into each other?
Great content and explanations! There were typos and discrepancies in the code that made for good challenges while trying to follow along (relatively new to Rust here), would have benefitted from having a link to the finished code
@@nyxtom Thanks!
Which tool do you use to record video and how do you prepare slides for this video. Amazing explaination
Thank you. This was an informative video.
Couple of notes:
- This video is LOONNGGGG (but that's ok, it's informative)
- Typo in the slide at 7:44, where /n should be
, but in fact it should be
as per RFC2616-2.2
- At 12:25 the parameter in the function argument is `path`, while you pass in `resource` to node.get
- the `let res = Response::new(client);` needs to be mutable (?) (before and up to 18:55)
- At 19:31 (unless i missed something) you never handled the else clause for handle/Some(handler) which would(should) check for a static file or return the 404 page
Side note: I skimmed over the forking/threading, since I already had that in place from another tutorial, I would say that I would avoid using libc::fork, since now you broke cross os compatibility, pretty sure fork doesn't exist on windows. and the usages of unsafe are can be avoided if you're just spawning threads from the threadpool. (unless there is some huge advantage over forking that I don't see?)
Other than that, I'm amazed how the quality of your videos increased significantly in only a few weeks! I really do love this presentation style that you've developed, it's very easy to follow.
Keep up the good work!
One request, since I can't find any good tutorial/documentation about it, if you know how;
I would like to know how to implement a custom `#get("/")` (for example) macro that eg, rocket uses for the routes.rs mod. If you could cover that in a future video, that'd be amazing.
Hello witch tools do you use to create your vid and illustration.?
I like the more advanced topics, but I didn't quite understand what was happening in the reader/line reader part around the 12 minute mark.
I understand it's to prevent an attack vector around user not sending newlines, but a diagram would have been helpful to show how "reader.fill_buf" works
Nice presentation but the title is a bit misleading. Expected to learn something about async (futures, await, etc...) but there's only info about parallelism based on OS threads.
That's too complex for me. For someone who has just started with rust, I feel it's going to be long and tough journey. Just a suggestion, could you also make some short tutorial series for Rust and side by side cover such advance topics..
If you are here you are no longer in the Rust for beginner TH-cam algorithms lol 😂😂😂
What is this... a new framework...?