Would it be possible if you could describe Threads vs Processes and how Operating systems manage processes? It is one of the more difficult concepts and I think your talent in teaching would be of great use. Other videos confuse more than clarify because they all seem to contradict each other on minor details. You give a great explanation because you describe these concepts on a large scope and abstract away trivialities.
Good idea, I'm genrally confused between the real thread (physical) and the virtual one , the meaning of thread in operating systems , When I create a thread in nodejs for example , does it mean that it will wait until a physical thread or virtual one runs it ? When I fork a process what happens in my cpu ?
@@brucewayne2480 just to make you more confuse, physical threads don't exist virtually, but virtual threads exists in physical when the realm changes from 3d to 2.5d, which makes os a software running on single thread and multiple virtual cores.
Hi, I'm a second year computer science student and I cannot stress how much this video was helpful to me, it really came in a time when I was struggling to understand some advanced computer networks concepts, I was actually struggling to design a protocol when I didn't even know what It means, thanks a lot man, the explanation was very good, simple and precise, I really appreciate it
I definitely like where these deep dives are headed. You have a wonderful way of boiling down complex subjects. My suggestions would be an exploration of SSL/TLS.
I speak Spanish, and having subtitles helps a lot to be able to understand everything you're saying, because I know English, but at a medium level. Also the fact that you explain things so thoroughly, starting from the base, makes your content great, I will follow this channel forever and I will always recommend it, among the best alternatives.
Great video! To even dive deeper: A very interesting part of TCP is also the Congestion Control to optimize bandwidth utilization. It is still a huge research field at e.g. Google and KIT...
This is possibly the best video about this topic I have ever seen, you are excellent at what you do! I appreciate the content and will keep visiting every time I can!
As computer/electronic engineer I was fed up with all this protocols/communications like this. UART, I2C, SPI, USB, ZigBee, BT or even CAN, but also many others. But with time I understood how much it helps when you go for higher level applications etc. GR8 lecture from yourself as usual.
Many people have understanding problem, so is this the video author. Protocol is just a way of communication between two parties. Very easy to understand. Just like two people meet one say "Hello", the other also say "Hello", one say "how are you doing today", the other say "Pretty good, how about you?"... Client and Server in communication have to follow certain protocol to communicate.
A good topic for a standalone video would be what is a program and what happens when i execute it. Of course that's such a broad topic that no one video can do it justice but i feel like there is a big gap between the layman's understanding (an exe file that just does things when i click on it) to the understanding of the program being run with arguments and then getting loaded into memory and what do all play into this. I don't have to many concrete ideas but from what I can see in my fellow CS first year's is that this something they don't really have a grasp on and just take it a some magic
Oh man, I have no words but just an exciting feeling to finally understood or just at least get a glimpse of these fundamental knowledge and not just hacking stuff. Wherever you are, Thank you LiveOverflow.
This is useful even for seasoned web developers imo, at least it was for me personally. It's good to re-solidify fundamentals from time to time! I hadn't thought of e.g. the Twitter API as a protocol, but it's obvious in retrospect.
Very informative video! If you end up making more I think going into how networks are structured might be an interesting topic (e.g. locally, when connecting to a website, in a lan configuration etc).
For network protocols, just grab Wireshark and see how they work. So far I implemented a UDP stack and a web server and it was easy. Also WebSocket. As a second step, reading the RFC helps a lot. Reverse engineering is a good way to start.
Just an additional bit of information, whenever going into the TCP protocol. In the TCP 3-way handshake (SYN, SYN & ACK, SYN), all of those are controlled within the TCP header in a section called "control bits". There's a total of 6 control bits that you can choose from; URG (Urgent, used to indicate packet priority), ACK (Acknowledgement, used to acknowledge connection was successfully established), PSH (Push), RST (Reset the connection when a timeout or error occurs), SYN (Synchronization), and FIN (Used to terminate connection)
extremely unvaluable content. I would also been very grateful for having content like this available when I was in university. It also helps now to clarify ideas and better understand all these. Thank you very much!
I kid u not, i'm ready to confess my love for you! The way it made so much sense! I always wanted to study programming and software development but ended up majoring in networks & cybersecurity, which is kinda confusing for me😭 you gave me hope i can actually do this
Man. I'm not a natural in IT and it`s often hard to UNDERSTAND why things as they are. Unfortunately, a lot of teachers and professors just say "So, here is *some concept* works like this, used for this" and forget to explain why it does even exists. If there is a solution, there is problem it tries ti solve. Thanks for the explanation.
I didn't even watch it yet, but I would have LOVED to have had this video like 4 weeks ago when I started my research paper on Internet Protocols... anyways, can't wait to watch it!
Charles Petzold's Code is a really great read imo that expands on this & goes over the historical context of shared communication protocols & their evolution. Worth a read! :D
Thanks for making this video. I hope that my comment from the last deepdive series video about what is a server partially helped you decide on this particular topic :)
thank you, this is my favorite segment in this channel. Maybe next you can explain Service Bus, Message Broker, Serialization, Interface, and other jargon in IT that made people confuse. Thanks a lot for video.
I really liked the video ! the word "Framework" is also a little bit confusing may mean some sort of "library" in programming language , may carry another meanings in the firmware and used in software design ..etc
Teachers in schools should be teaching the way you do, by logically explaining each step of the way but unfortunately the main method of teaching in schools is by memorization. Much of that is do to the fact most people don’t know how to break down the thoughts to the “smallest atom”. Awesome explanation. You should be a university professor.
Very nice explanation, helpful to capture get a grasp on a big picture about protocols. I am now learning about the in HTB academy and I've found it very insightful. Thanks!
Vielen lieben Dank für deine inhaltsreichen und intelligenten Videos !! Educational und wisdoms filled !! Awesome stuff !! Greetings from California … Ich wünsche dir euch gute Gesundheit, Erfolg und Freude !! Much Love ✌️😎💕
Wow! Dude. You think exact the same way that I think and I was wondering about such things. I really wanted to get what they really means. Now I get it. Thank you!
UDP is like sending postcards. You cut whatever you want to send into small pieces, write it onto the back of a postcard and send it. The receiver then has to sort through a whole stack of postcards and puzzle out the order and if some are missing or not. TCP is like making a phone call. You call someone and get 2 continuous channels where not only every word you say is delivered in the exact same order to the recipient, but you also know if the call is established or ended. IP is like UDP, but the postcards only have street and city but not apartment number or recipient name. The postal service doesn't care about those, they only are needed after the postcard has reached the destination address. That's why IP is used as a layer under both UDP and TCP.
it would be interesting to hear your thoughts on the QUIC protocol. As well as if you think it could superceed TCP in time. Also a video on QUIC (RFC 9312) seems like a nice progression from a video on TCP
I struggle a lot with understanding hardware documentations for microcontrollers. I don't know where to begin, because everythings just seems to be cryptic or only for extremely clever people xD. Maybe u can make a video, how and where to start with hardware programming/microcontrollers, hardware hacking etc. This would be extremely helpful^^. Great video!
This really explains something that has only been hinted at recently when terms like PPEoE/PPPoA became common parlance due to broadband. This literally describes the function of nested protocols in action the o represents over thus in both cases PPP (point-to-point) is encapsulated in something else, PPPoE means you are sending PPP over Ethernet, PPPoA is over ATM. But there are more layers if you have a PPEoE connection and attempt to read youtube you are sending SSL over HTTP over TCP over IP over Ethernet to your ISP. In short you are encrypting your data sending it over HTTP which uses TCP and IP via your router which basically assumes the rest of the world has just one IP (PPP). These layers of abstraction get stripped as your message heads to the destination, your ISP strips the PPP and ATM/Ethernet layers. IP transit then gets the packet to the server which then uses the TCP layer to figure out which program to wake up to process the payload.
I've never seen anyone explain things as good as you do
because he really understands it xD
true
His headline is enough isn't it
Would it be possible if you could describe Threads vs Processes and how Operating systems manage processes? It is one of the more difficult concepts and I think your talent in teaching would be of great use. Other videos confuse more than clarify because they all seem to contradict each other on minor details. You give a great explanation because you describe these concepts on a large scope and abstract away trivialities.
Good idea
+100
Good idea, I'm genrally confused between the real thread (physical) and the virtual one , the meaning of thread in operating systems ,
When I create a thread in nodejs for example , does it mean that it will wait until a physical thread or virtual one runs it ?
When I fork a process what happens in my cpu ?
@@brucewayne2480 just to make you more confuse, physical threads don't exist virtually, but virtual threads exists in physical when the realm changes from 3d to 2.5d, which makes os a software running on single thread and multiple virtual cores.
@@Miles-co5xm :/ !
This Deepdive series is fire 🔥
Keep doing the good work, sir!
Man, he should go deeper and wider with a complete tutorial on Computer Networks academic level!
Please make more (Deepdive) videos! They Are great and very informative
Hi, I'm a second year computer science student and I cannot stress how much this video was helpful to me, it really came in a time when I was struggling to understand some advanced computer networks concepts, I was actually struggling to design a protocol when I didn't even know what It means, thanks a lot man, the explanation was very good, simple and precise, I really appreciate it
You're warming up to me, Finally Explaining stuff without a passive Condescending Tone , Amazingly Done 👍🏾
I definitely like where these deep dives are headed. You have a wonderful way of boiling down complex subjects. My suggestions would be an exploration of SSL/TLS.
I speak Spanish, and having subtitles helps a lot to be able to understand everything you're saying, because I know English, but at a medium level.
Also the fact that you explain things so thoroughly, starting from the base, makes your content great, I will follow this channel forever and I will always recommend it, among the best alternatives.
This series is proving to be the one is always wished for.
Great video!
To even dive deeper:
A very interesting part of TCP is also the Congestion Control to optimize bandwidth utilization. It is still a huge research field at e.g. Google and KIT...
Man you make this so fun and easy to digest with the supportive visuals
Your way of explaining things is the best I've ever seen.
This is possibly the best video about this topic I have ever seen, you are excellent at what you do! I appreciate the content and will keep visiting every time I can!
You made the server concept "click" for me.
please continue this deepdive series as more topics need to be unraveled like this
As computer/electronic engineer I was fed up with all this protocols/communications like this. UART, I2C, SPI, USB, ZigBee, BT or even CAN, but also many others.
But with time I understood how much it helps when you go for higher level applications etc.
GR8 lecture from yourself as usual.
This deepdive series is invaluable....please keep doing this
please never stop making such videos
Great explanation!!!
Please make more such videos on other networking basic concepts
Cheers!
Many people have understanding problem, so is this the video author. Protocol is just a way of communication between two parties. Very easy to understand. Just like two people meet one say "Hello", the other also say "Hello", one say "how are you doing today", the other say "Pretty good, how about you?"...
Client and Server in communication have to follow certain protocol to communicate.
Wow ! This is a great explantion and i like how you reference the RFC's . Great timing on this changed my whole paradigm on Protocols for life.
Anyone who goes through the time to read and implement those protocols (by reading the RFCs) are.... mad lads
i think you're gonna finally taught me what networking is all about. I bet your 17 year old self is grateful to you!!!
A good topic for a standalone video would be what is a program and what happens when i execute it. Of course that's such a broad topic that no one video can do it justice but i feel like there is a big gap between the layman's understanding (an exe file that just does things when i click on it) to the understanding of the program being run with arguments and then getting loaded into memory and what do all play into this. I don't have to many concrete ideas but from what I can see in my fellow CS first year's is that this something they don't really have a grasp on and just take it a some magic
Oh man, I have no words but just an exciting feeling to finally understood or just at least get a glimpse of these fundamental knowledge and not just hacking stuff. Wherever you are, Thank you LiveOverflow.
This is useful even for seasoned web developers imo, at least it was for me personally. It's good to re-solidify fundamentals from time to time! I hadn't thought of e.g. the Twitter API as a protocol, but it's obvious in retrospect.
This is amazing as a web developer I'm very grateful for explaining it so well for me!
I have been watching RUclips for a better part of my life and his video's 15 sec intro just made me subscribe love the honesty and motivation.
Very informative video! If you end up making more I think going into how networks are structured might be an interesting topic (e.g. locally, when connecting to a website, in a lan configuration etc).
For network protocols, just grab Wireshark and see how they work. So far I implemented a UDP stack and a web server and it was easy. Also WebSocket. As a second step, reading the RFC helps a lot. Reverse engineering is a good way to start.
Just an additional bit of information, whenever going into the TCP protocol.
In the TCP 3-way handshake (SYN, SYN & ACK, SYN), all of those are controlled within the TCP header in a section called "control bits". There's a total of 6 control bits that you can choose from; URG (Urgent, used to indicate packet priority), ACK (Acknowledgement, used to acknowledge connection was successfully established), PSH (Push), RST (Reset the connection when a timeout or error occurs), SYN (Synchronization), and FIN (Used to terminate connection)
Another great explanation!. Kindly make a deep-dive video on OSI Model.
extremely unvaluable content. I would also been very grateful for having content like this available when I was in university. It also helps now to clarify ideas and better understand all these. Thank you very much!
I kid u not, i'm ready to confess my love for you! The way it made so much sense! I always wanted to study programming and software development but ended up majoring in networks & cybersecurity, which is kinda confusing for me😭 you gave me hope i can actually do this
Really, really great explanation. Loved the examples too - helped me finally understand HTTP requests. Keep it up :)
Man. I'm not a natural in IT and it`s often hard to UNDERSTAND why things as they are. Unfortunately, a lot of teachers and professors just say "So, here is *some concept* works like this, used for this" and forget to explain why it does even exists. If there is a solution, there is problem it tries ti solve. Thanks for the explanation.
I didn't even watch it yet, but I would have LOVED to have had this video like 4 weeks ago when I started my research paper on Internet Protocols... anyways, can't wait to watch it!
Thank youuuu, the best explanation ever.
16:15 takeaway.
Charles Petzold's Code is a really great read imo that expands on this & goes over the historical context of shared communication protocols & their evolution. Worth a read! :D
This video is really crazy, clearly explained everything with examples
Amazing video, I didn't really learn anything new, but your "style" of explaining things is really good.
Amazing video, the way you explain things is the best. Please make more videos deepdive like this.
I love how you have explained the Protocols
I love this format! Awesome video dude 🤙
Thanks for making this video. I hope that my comment from the last deepdive series video about what is a server partially helped you decide on this particular topic :)
Thanks for the good video. It cleared many of my doubts.
Thank you so much for this video. Much needed one for me. Please continue this deepdive as a series.
You are a gifted teacher. Period.
thank you, this is my favorite segment in this channel. Maybe next you can explain Service Bus, Message Broker, Serialization, Interface, and other jargon in IT that made people confuse. Thanks a lot for video.
This is what i am searching for since 3 months thank you
I really liked the video !
the word "Framework" is also a little bit confusing
may mean some sort of "library" in programming language , may carry another meanings in the firmware and used in software design ..etc
Bro I just got into cyber security and I was confused about protocols. This video helped me a lot 🙏🙏
Teachers in schools should be teaching the way you do, by logically explaining each step of the way but unfortunately the main method of teaching in schools is by memorization. Much of that is do to the fact most people don’t know how to break down the thoughts to the “smallest atom”. Awesome explanation. You should be a university professor.
a video that i wish existed back when I was learning protocols, great job !!
This video is the answer to my search for the question for so long!
I love the deepdive series so much! I never knew about protocol this far!
This kind of videos are very very cool 👌
I love it 💚
Love it! I'm hearing a Telematics lecture this semester and these Videos are a great addition to help my basic understanding of the subject. Thanks :)
Nice video! BTW, tip for at 2:00, "suite" is a loan word from French and is pronounced like "sweet"
This is the best explanation I've seen about this topic! Good stuff man
You have the best explanation skills! Thank you for this!! :)
Great video as always. I've often found the concept of protocols a bit enigmatic but this was really helpful!
This was awesome! the term that confused / bugged me for the longest time was “pattern”
This was a very good video explaining protocols in the finest details! I would definitely show this to a friend if they asked me about a this.
Bravo! Simple and at the same time magical!
Very nice explanation, helpful to capture get a grasp on a big picture about protocols. I am now learning about the in HTB academy and I've found it very insightful. Thanks!
You are such a good teacher. Thank you for your videos.
Thanks! I love figuring out exactly how things work and this really helped me with that!
Vielen lieben Dank für deine inhaltsreichen und intelligenten Videos !! Educational und wisdoms filled !! Awesome stuff !!
Greetings from California … Ich wünsche dir euch gute Gesundheit, Erfolg und Freude !! Much Love ✌️😎💕
Wow! Dude. You think exact the same way that I think and I was wondering about such things. I really wanted to get what they really means. Now I get it. Thank you!
More Deepdive please. Amazing content!
your hardworking must be appreciate!
Amazing explaination sir ! Really helpfull for a freshman like me
UDP is like sending postcards. You cut whatever you want to send into small pieces, write it onto the back of a postcard and send it. The receiver then has to sort through a whole stack of postcards and puzzle out the order and if some are missing or not.
TCP is like making a phone call. You call someone and get 2 continuous channels where not only every word you say is delivered in the exact same order to the recipient, but you also know if the call is established or ended.
IP is like UDP, but the postcards only have street and city but not apartment number or recipient name. The postal service doesn't care about those, they only are needed after the postcard has reached the destination address. That's why IP is used as a layer under both UDP and TCP.
Very good video. I actually have a short oral exam in two days of how UDP, TCP and some others exactly work and this video was very helpfull :^)
I would be very happy if you made more videos like this.
Excellent explanation - clear and concise!
Thank u for the informative video! It really helps me to understand what is protocol.
Thank you im in the industry and this is refreshing.
This is such a great video. It helped me a lot to consolidate my knowledge and to see learning from a new perspective. Thank you.
Yep, That's what I was looking for !!! Awesome work
Great video,love it . Would love to see a video about certificates and their working
Amazing. I will implement networked Multiplayer to the game I am working on next year, this has been a good introduction :)
Love this series. More of anything please!
This video was amazing! I took lots of notes from it, you're inspiring!
😍😍😍😍 your explanation is too good man really appreciate how you tell everything 👍👍👍🤩
We need more network deep dive
Very detail but easy to understand video! Thanks
Great Video! :D
Another interesting topic for a video would be the OSI Model.
You are so much more helpfull than my teacher.
Thank you for this awsome explanation. Looking forward to more of these videos from you.
it would be interesting to hear your thoughts on the QUIC protocol. As well as if you think it could superceed TCP in time. Also a video on QUIC (RFC 9312) seems like a nice progression from a video on TCP
Just went and looked QUIC up - seems interesting!
I agree
❤the best explanation I have encountered! Thanks ❤
Hands down for this guy.
I've never met a better demystifier on youtube; not even the highly revered Indian guys.
This was a REALLY amazing video, just fantastic
That's exactly what I need, now while I'm learning coding
Perfect explanation!!!
Please make videos about SMB or LDAP
finally! it's all begining to make sense! thank you :)
These Deepdive videos are awesome keep them coming :)
I absolutely love you.
What a method man.
I struggle a lot with understanding hardware documentations for microcontrollers. I don't know where to begin, because everythings just seems to be cryptic or only for extremely clever people xD. Maybe u can make a video, how and where to start with hardware programming/microcontrollers, hardware hacking etc. This would be extremely helpful^^.
Great video!
This really explains something that has only been hinted at recently when terms like PPEoE/PPPoA became common parlance due to broadband. This literally describes the function of nested protocols in action the o represents over thus in both cases PPP (point-to-point) is encapsulated in something else, PPPoE means you are sending PPP over Ethernet, PPPoA is over ATM. But there are more layers if you have a PPEoE connection and attempt to read youtube you are sending SSL over HTTP over TCP over IP over Ethernet to your ISP. In short you are encrypting your data sending it over HTTP which uses TCP and IP via your router which basically assumes the rest of the world has just one IP (PPP). These layers of abstraction get stripped as your message heads to the destination, your ISP strips the PPP and ATM/Ethernet layers. IP transit then gets the packet to the server which then uses the TCP layer to figure out which program to wake up to process the payload.
Amazing explanation!!! Thank you so much