This was so good i would just like to say. And my great great great grandson, William, is very primed and ready to tell you about u8 and their downfall

Absolutely great video. You managed to cover almost everything and keep it simple. There's only one huge problem. I'm 257 years old and that invalidates everything.

This guy is one of the better discoveries I've made on UKposts in quite some time. This is helping me pass my Operating Systems exam. Btw, books referenced couple of times in your videos are the same ones I'm currently learning from. Great minds think alike. 👍

I think they were just mad that vampires ages would be excluded by that u8

according to that commentor we cannot write any program because the parameters of our living world may change any second...

I'm a self taught developer, so your videos fill many gaps in my knowledge of architecture. Keep doing them! You're a gem on youtube!

Excellent video. By far the most educated explanation to stack vs heap without digging unnecessarily deep to lose the point. I love the part you reiterate what “heap is slow” actually means “heap allocation is slow”. Would love to see a follow up video on how to access heap fast by leveraging cache-line alignment, packed data structure etc. from day to day i got worried about accessing the heap memory in hot path, even it is a pre-allcoated once vector to be reused for each loop - i can’t reason about for every loop whether or not pre-allocating a dynamic size vector on the heap (and perform a clear upon each loop) or use a large enough fix sized array so it’s on the stack always (although potentially waste of memory coz you can only expect the worst case size of an array at compile time) Looking forward to the next video. Greatly appreciated

F I N A L L Y! Someone that doesn't go high-level but rather goes in depth to provide low-level content that is presented very elegantly!!! SUBBED

That "as an AI model" jab with the voice was hilarious. This was a great refresher since I could hardly remember anything from my own operating systems unit.

Great video! Good explanations at a nice intermediate level! I can see a couple of things to add for a bit more depth. First, the performance problem with allocating memory on the heap is a good example of where it's more about the variance (or unpredictability) than the typical case. For most reasonable heap implementations and kernel page allocators, allocations will be really fast, but a small number of times, it's going to be really slow, and that can have significant impact on "quality of service". Second, in that vein too, I would say the overhead of requesting memory from the OS / kernel isn't really the context switch. That's pretty negligible compared to page allocation. What's really bad is the kernel lock. The point is that the kernel has to deal with multiple processes requesting memory at the same time, and so, it has to have a global lock to synchronize those allocations between processes. Clever things can be done to avoid hitting that lock too much, but it still has to be there and you will inevitably hit it. This is one of the few places where multiple processes on a system directly interfere with one another (beyond just generally sharing limited CPU/Mem resources). And kernel locks can be a big deal, I've seen wait times in the order of a few seconds when hitting a kernel lock, which can be a major disruption in the middle of an operation you expect will only take a few milliseconds.

0:55 bro got publicly humiliated💀

This video is EXCELLENT! Like you said at the start, there's some simplifications-but it's totally accurate and very comprehensive. I'm one of those "more experienced people" you mentioned at the start (at the end of an extended 6-year undergrad in compsci), and I'm impressed by how much info has been crammed in here. I'm about to start a master's degree with a focus on pedagogy (the study of teaching), so you can imagine I spend a lot of time explaining these topics to my juniors. I think you've found an excellent level to simplify things to for someone who may be new to this sort of thing. Good examples always help, and you transition to them well and the "story" of the video flows well. Great work on this video. I'm going to go and watch the first video on the stack, too. Even if I've thought about this stuff a ton over the years, this was a great refresher on a few of the concepts I've gotten rusty on (pun not intended) or even completely forgotten about. Looking forward to the next video!! 😄

Such an informative video, the visualization and commentary deserves a lot of credit. I enjoyed it thoroughly!

Heap and stack management are two of the most fundamental topics in programming languages, and understanding them can spare a lot of headaches so you can secure and debug your program easily. Thank you for your videos. Keep it up.

I feel extremely lucky to have found this video. Very informative. Please continue on making more of these ones.

Yooooo, this video and explanation are amazing, I have been having a vague concept of thes topics for a while now, but this really helped me grasp it much better. So thanks a ton for all the effort in the animation and script!

This is an extremely well explained video or at least one of the best introduction I've ever found. Please continue with same kind of format. I've just subscribed to your channel.

Excellent explanation of complex concepts! I wish if you can cover Booting, BIOS and UEFI in detail along with MBR and GPT partition internals. Namespaces, CGroups and File systems deep dive

After I wrote a compiler, I realized that a lot of the power comes from the fact that you can use relative references from the knowledge you have about the stack at compile time, which makes it so powerful. There is no lookup, it just knows the address of the variable you are trying to access. This was after optimizations, at the layer of code generation.

Men I've watched all your videos and I have to say it: impresive. Very well explained (even with the simplification which is 100% necessary). Keep it up, nice work :)

Tysm for making these. I've been learning Rust lately, and as part of that I've been trying to learn how to best use the low level features it provides. I've gotten the hang of references and am getting to grips with lifetimes, and learning about things like the heap and stack are helping a lot with learning what Rust is doing and what it's protecting me against when it's particularly strict in a region

I am really loving your content. You're doing an amazing work, I can't wait to see more of your videos!

You're one of the best out there for explaining weird prgramming concepts that are obscure for some of us, your videos are of very high quality and very well explained. I am really looking forwars that arraylist video tho, that tickled my curiosity.

My new favorite YT channel. So amazing, cant wait to see more

1:15 hahahaha youtube channel named "ThePrimePrimePrimePrimePrimeagen"

This is the type of video I have been looking for, great work keep up the good work!

Thank you, Been trying to learn some of the low-level stuff on my own and this video is amazing. Can't wait to see the next one!

I love your series! I’m looking forward to the next one! Thank you!

well explained.. thank you so much... happy to see more content explaining underlying things like this ❤. soo happy about finding this channel

Excellent!! I’ve never watched an in-depth well explained video about heap and stack like this one!

i knowing every thing you explained in this video but your way to explain things is incredible, thank you keep going

What an amazing video! The way you explain things are so simple to understand! Well deserved subscriber number in short amount of time!

Please keep these videos coming! I'm coming from Javascript with very limited insight into the amazing world of low-level programming. I'm currently learning C and your videos got me hooked!

Thank you so much for the effort you're putting in those videos ❤

I have never seen this so well-explained. Excellent job! This series of videos will be my go-to resources for teaching others these low-level concepts.

Videos like these are really helpful as they help visualise the key concepts we learn in computer science. Take data structures for example, I kind of knew why we use them but seeing an animation for it really helps clear things up. I hope we get a series about the different data structures and their needs too.

I've been getting a lot into memory management and i gotta say this is the best video ive found. You answered all my questions and just explained everything perfectly! Also the AI voice didn't bother me much after a few minutes. Thanks for sharing this and please continue to make more!

The comment put on blast in this video makes me think of something John Carmack said in his appearance on Lex Fridman's podcast; I'm definitely paraphrasing, but Carmack said something about how it can be useful to include limitations in your software that will notify you when things have changed greater than you ever thought they would. He was speaking in reference to limit-removing ports of the Doom engine, but I think it's pertinent here too. It's okay to write software that addresses your current needs and your current use case using the technology currently available, and sometimes that will force you back to the drawing board to some extent in the event that something related to your needs, use case, or technology changes, but that's not necessarily a bad thing even if it causes more work, because if something has changed that much, it's quite likely that other things have also changed such that other parts of your software need to be revised or at least reevaluated. So basically, what I'm saying is that the event of maximum human lifespan more than doubling from its current state would probably be part of much broader and more sweeping changes to the world that would call for a more holistic revision of your software. But because there does not seem to be any realistic probability in any remotely foreseeable future of a human being living to age 256, it is perfectly reasonable and sensible to represent human age with a u8.

Please don’t ever stop making videos! These are awesome!

An amazing explanation for someone who has experience programming but not in a language or context where I ever have had to think about or learn this stuff. Thanks!

bro thanks for the videos. the animations you used really helped with my understanding. i look forward to more vids

Best video that connects everything from top level to bottom level.

Love this video. Very informational. I would even consider videos like this as complementary to even the best CS course on OSs.

we appreciate your efforts , waiting for more in depth videos

I love the level of Reddit “well actually” from that comment, the part about ages going over 256 years being a Y2K bug waiting to happen is gold because you didn’t build your software to last. Glorious.

There's one more thing that can make stack faster. Instructions may use immediate addressing relative to the stack pointer. Accessing data on the heap requires loading its address to a register first (not on all architectures), which not only is an extra instruction but additionally makes that register unavailable for anything else.

As a senior engineer, this is an important lesson to learn for junior. Heap is fast and can be fast, it's all about how you design your data structure. For example with linked list, one can implemented with contiguous vector as storage ( you must manage the free slot a bit ), and it can be really fast.

Great. You covered the heap in a lovely and intuitive way. The only thing is that I would add would be alternative allocation techniques such as arena allocators their upsides and downsides.

Thank you for the video Sir, It was great ! Can't wait for another one.

Learning about memories made me look at programs a lot differently. Thank you good sir for making videos like this.

Keep it up! These videos are very helpful.

I was just looking for video like this. Awesome explanation, George.

Excellent content! Keep up the great work!

Didnt really have time for this now, but this is so well made with so few subs that I just have to let the alog know this is great!

Can't wait for your future videos! I love learning low level concepts like this

Your work is amazing!

This and the previous video has illuminated so much for me .. I'd be really eager to see a video on "memory leaks" as a follow up to this.

You are amazing. I always subscribe to anyone who explains us with amazing detailed animation. Thanks.

This is really informative. Keep making more videos. Subscribed 😊

Wow, you're producing good content here, subscribed! Clear explanations and diagrams, kudos.

Great channel, thank you for your work

this was an awesome video.... keep up the good works and thank you.

Very good and quality content! Keep up the good work!

As a Python, Lua and Bash wannabe scripter, im happy to have discovered your channel. I showed your other videos to a freind struggling to shift from c++ to python and he was amazed, we both understood how and why pointers generally work in c++, stack overflow and how high level vs low level fundamentally differ in both code and under the hood. Im also inspired, though ive to 1st finish some high level language battles. Im even heavily conflicted between c++ and Rust, its going to be a challenge but aint that the beauty of language ( moving diffrent parts within certain parameters to attain certain output ... like the way we arrange nouns, verbs and adjectives in this foreign language to get an output/meaning). Thanks... Arigato and Valar Morgulis.

dude, I love you. This is the best explanation I've ever found so far

I showered praise on you for the Stack video... and you've outdone yourself with this one! You could easily be a required supplemental instruction to CS50, and it would actually make the course clearer and more intuitive :) Can't wait to see these other teased videos, such as vectors and other data structures!!!

Bro your videos are so cool and interesting. As a CS student this is so helpful to fill in the many gaps of understanding. Thank you

ooooohhhh, okay NOW I understand when something goes on the stack or the heap and why. I'd watched and read other resources explaining this, but never quite got it until your explanation here. Thank you! =)

Thank you, I am a C progammer from the 90's and have a project I need to get back into. All the bits came back in my head on Heap and Stack

I love your content dude, this is the 3blue1brown level of simplicity and clarity combined with helpful visuals. 10 / 10

One of the best channels at explaining low level concepts, i have just started with C recently in hope to learn about these things more and later on go to rust, and i must say you are really good (even as a LLM haha)

Dude, great content, I think this channel is going to be a bomb! Keep up with the amazing work!

Thanks for the knowledge!

Exceptionally good job. Thank you

Thank you, what an instructive video! 18 minutes well spent. ive been foggy on this topic for years

Please make more videos, appercitate your hardwork, you explain in a simple way and easy to understand, thank you so much!!!!!

Amazing videos, please keep them coming!!

You know in the past two months I spent weeks reading and searching on these low level concepts (explained in details more or less) after losing hope on UKposts. Thankfully there is someone today 😇

Very well done, many thanks!

Exceptionally well explained!

The most awaited video 🔥

Excellent vidéo, can’t wait to see the next ones

I’ve studied programming on and off in many forms for a long time. This is the first time I have seen an example of how a linked list interacts with memory fragmentation. The others all just explain the big O’s and that’s it. They don’t ever encourage thinking and reasoning about runtime. Good job! Thanks for this. Liked and subscribed! (I wonder if the algo triggers on exclamation marks, let’s try that !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)

Thanks for this trip down memory lane. About 20 years ago a big difference between C# or C++ became a 3 hour daily commute for the latter. The linked list option is easy to forget, useful in higher level languages too.

Keep going I.A. you are doing a great job!

Thank you very much. That's the simplest and easiest video to understand.

fantastic visualization and explanation

for people like me your channel is immensely helpful for example now I understand why we need data structures like linked lists. I hope you keep on producing awesome content. This is like Nand-to-Tetris but more visual. Thanks.

Congratz for the great video bro! Thanks for share

I can’t wait to see your next videos. These videos are phenomenal crash courses to us new devs

Maaaaan. Great videos. Thank you so much.

That was such a good explanation, bless the YT algorithm for introducing me to your channel.

I wait for your explanations bro keep uploading you are one of the best cs explaining guy I ever found😇

feels like i'm back in systems class back in university .. great work!

You explain it well , We are waiting for the next videos

Thanks for this video, it was quality! Shared it with fellow boot.dev'ers who really haven't heard of the Stack/Heap. Also for me it was really nice to see the inner details of a sys call, because to my own demise, I knew there was more overhead from it, but never looked up what actually was happening. 10/10 vid!

A very good explanation, thank you.

long videos are good! looking forward to the continuations

For the amount of work put into these videos, you deserve more subs

Stuff like this is why programming is magic/wizardry to me. I understand the logical concepts, but wielding it is another thing entirely. I also see why (in part) programming is so difficult and error prone.