These ideas were saved in my head as a sequence of words for the entirety of my undergrad. If 5 short minutes you managed to actually help me understand a huge gap in my understanding. Thank you so much.
@@alexhyettdev public class Main { String s = "ABC"; public static void main(String[] args) { Main obj = new Main() ; System.out.println(obj.s); } } in this above code String object is created in heap and also of class. So 2 objects in heap. But isn't the string object Abc resides inside class object in the heap?that's why we are calling it obj.s
@@alexhyettdev Quick question. You mentioned that when a pointer/ref in the stack is deleted, the value it points to dangles around the heap until the GC collects it, but what happens in a language like C++ there is not GC? Would that become a memory leak?
Alex, you made my day. I would call you one of the best instructors! Your explanations are flawless. You explain perfectly in context. For instance, where you explain why variables are not accessible outside the method.
YOU ARE LITERALLY CAPABLE OF REPLACING 99 PERCENT OF TEACHERS WHO PATHETICALLY FAILED TO TEACH ME THIS CONCEPT. THE CLARITY WITH WHICH YOU JUST EXPLAINED IT SHOWS THE TRUE MASTERCLASS YOU ARE IN. I WISH I DINT WASTE MONEY IN COLLEGE WHEN PEOPLE LIKE YOU EXIST. LOVE YOU SIR ❤
Not gonna lie, i cant state enough how explanations like this can massively improve your understanding of why code works the way it does. Just learning to code is one thing, but understanding whats behind all of it and WHY whatever thing actually is happening, can definitly up your game. Im not a pro by any means, but i think stuff like this is very important. The visual presentation also makes it way easier to follow and connect the concepts - so thx for that 😊
Thank you, I am glad you enjoyed the video. I find it helps with remembering everything as well. If you can understand something then it tends to stick in your mind a bit better.
Thank you sir. Good Explanation. Please, I wish you make a video on "Why in Java, Do Local Variables Used in Lambdas Have to Be Final or Effectively Final?" and please make the explanations at the memory level too, so we can understand all the mechanics behind it.
Reading a book right now that explains this concept rather poorly over 20 pages. You managed to grant me understanding in 5 minutes, and now I can continue reading past the chapter. Thank you, great explanation!
"Whenever you run anything asynchronously, it's gonna get run in a different thread." This is a wrong statement , asynchronous operations can use the same thread.
Finally a much simpler with actual sample code that explain the whole stack and heap stuff. Now I understand why and when OOM occurs in app, the usual suggestion is to increase heap size but said to be slow or when we do recursion recklessly we get stackoverflow.
This is an excellent video about how the memory works, I love the last part about asynchronous methods. Thank you for this awesome content. I wish you could speak more about asynchronous functions. 😃
While asynchronous methods can run on different threads, they do not necessarily have to. Aync execution can also involve single-threaded environments. E.g.: with event loops (JavaScript / Python's asyncio)
I've been coding, and teaching code for the past 4 years. This video blew me away. Explained everything so well, and was incredibly easy to follow. Sorry, Alex, I will be stealing this! Amazing work, and you've got a new fan! Thank you!
Can you re-check this one? I think something is incorrect with global or static variables. We basically have 4 segments: Stack, Heap, Code Segment, and Data Segment. Global or static variables, including constants like `const int MAX_AGE = 99`, are not stored on the heap. They are typically stored in the Data segment of the memory, specifically in the initialized data section. The Data segment is a part of the memory that contains static and global variables. These variables are allocated and initialized before the program starts executing. The initialized data section of the Data segment holds variables that have explicit initial values, such as the MAX_AGE constant in your example.
In C#, async methods that complete sync, before you await them, will not go onto the heap, hence the reason we have ValueTask now. However, if you use a ValueTask struct and it doesn’t complete sync, then you incur a hit of boxing, allocation, and deallocation (GC collect), which makes it a tiny bit more expensive than the regular Task class. One more thing. If you cast any value type to an Interface type, it will go onto the heap, even if it’s a struct or value type.
Many thanks to your video, this UA-cam is valuable, so I read word by word carefully. And I find at 03:55, about the static variable, which is different from what you mentioned in your flvog (the link you provide in descriptions). In ur flvog, in para "where do static variable live", there you said static variables even if they are value types are not stored on the stack or the heap...need clarify? Thanks.
Thanks for spotting the discrepancy! I need to update my blog to make things clearer. Basically it is an implementation detail. In C# static variables are part of the MethodTables on the "High Frequency Heap". Which is a special part of the Heap memory for static variables and internal data structures. In C and C++ they are stored on the Data Segment, which is a special part of the memory for storing static variables and internal data structures. :) Sound familiar? If you look up Data Segment and High Frequency Heap they are both in the same place in memory. By the looks of things they are just slightly different implementations of the same thing. There is an old article here that explains it in depth: web.archive.org/web/20140724084944/msdn.microsoft.com/en-us/magazine/cc163791.aspx Jon Skeet also has a good article on it as well: jonskeet.uk/csharp/memory.html
Hello sir at 3:20 in the video you say that in must run times there is a garbage collector that will clean the memory from the stored memory location after it has finished execution. Not sure if you know but with in C and C++ language we do not have a garbage collector I was told. So in C and C++ we delete pointers manually after block execution. So, Actually C and C++ are not garbage collecting languages.
I loved the explanation, just a small feedback you have tried to make the video stunning. Since you sit in a dark room and you are showing code on white screen its really painful for the eyes. Also this effect of your video zooming in out its very annoying. All the best and keep up with the good content
My jaw dropped when you explained what happens to variables declared in the stack, I never made the connection between this fact and the scope of variables, thank you soooo much !!!
Really nice explanation but I have one doubt, I used to think that global variables are stored outside of both stack and heap in a dedicated area for global and static variables. Would be great if someone could clarify on that.
@4:23 what do you mean by the anonymous function is pushed on top of the stack and not have access to what previous level down? You mean even variables within main?
Good video. One question: In the case of results from asynchronous methods, once the asynchronous function completes, who cleans up the result in the heap that was left over by the async function?
This was not at all useful to me. There's different uses of system memory. Program memory - a copy of the actual program in system memory, usually completely static. Execution memory - any allocated memory that could die at an unknown time (from the point of view of the OS) - the typical "heap". Local memory - value storage, exactly as you described it. Then there's the actual hardware - filesystem storage, system memory, CPU cache, GPU cache...
I wonder why we don’t have a heap stack. In theory, programs are hierarchical, at the top are all the values that live for the lifetime of the program. Below that, there are things that will exist for a shorter duration as different functions/methods are called. Eg in a web app, there are values and objects that are created to manage the web application, then for each request, there are values and objects created specifically for each request that don’t need to hang around after the request. And within each request, there are further subdivisions of lifetimes that don’t need to hand around for the full duration of the request. In theory, all the values and objects specific to the request could be put in its own heap, and on completion that heap gets cleaned up. Anything that should remain after the request would be on a different parent heap with a longer lifetime. The running program could keep statistics of the size of the heap required for different parts of the application. Maybe garbage collection already works this way though. But I don’t think so, eg with .net and the generational garbage collector. Maybe the programming language that have explicit lifetimes or ability to manually control allocations have this.
That's literally just a heap and a stack, but stuck together. I don't see the benefit or how that solves a problem. It might make a new problem though. Resist the temptation to fix what isn't broken.
Thank you. I am glad it is useful for people learning Rust as well. Some of the C# references might not be applicable but hopefully the rest is. I need to learn rust as well actually!
Learning assembly will teach you this better than I can. It's a mixture of CPU registers that hold references to areas in RAM that represent the stack abstraction. The data lives in RAM but the CPU registers are key to understanding the flow I think.
Is this what a memory leak is? If something like c++ that doesn’t have garbage collection or something gets left on the heap is that memory leaks or is that something else?
Yes exactly, languages like C++ which don't have a garbage collector need the programmer to release the memory correctly. If they don't then memory stays allocated on the heap and can't be accessed by anything causing a memory leak.
Great explanation! Thank you! My only bit of feedback would be to stay on the graphic visualizations longer. The constant switching between the visualizations and the shot of you talking is a bit jarring and makes it harder to focus.
"In a previous video" you talked about value type and reference type... can we get a link to that? I found a playlist but this is the first video in it.. there is no previous video
I have only started making courses recently. My first course on Solid came out 3 weeks ago: dometrain.com/course/from-zero-to-hero-solid-principles-for-csharp-developers/
Yes Stack and Heap are stored in the RAM. ROM doesn't have a stack or heap as ROM is Read Only Memory. It is written once and can't be changed. It is typically used for low level code such as the BIOS. Although even that is usually stored on Electronically Erasable ROM (EEROM) so that it can be updated. All of the applications on your computer including the OS will use the RAM. Stack and Heap are just ways in which the memory is structured to store your application code.
3:01 small correction. A const is NOT allocated on the heap. In fact, it's embedded on the call site at compile time (in C#/F#/VB), the reference is removed (you can test this: create a const in another lib, reference and use it in your lib. Compile. Now update the const in the referenced lib and recompile, but do not recompile your lib. You'll see it did not change on the call site). What you probably want is readonly, which, in your example at 3:01, would then be allocated on the heap.
How does garbage collection handle memory fragmentation? Is there a heap defrag utility? Do you wipe the heap when a program ends? What is multiple programs / threads run concurrently? Now I need to check the rest of your videos for answers. Thank you for starting my journey.
Incredible. Even though I've been a professional developer for six years, I was having a crisis of confidence tonight because I've worked with languages where I never have to worry about this directly. I was asking myself, "Do I even know anything about computers if I don't know the difference between the stack and the heap?" Five minutes and twenty-seven seconds later, I feel like I have a solid understanding of the difference and I'd be capable of talking about this intelligently. Thank you 🙏
suppose a function a returns another function b, that returned function b has reference to local variable x in a, now in stack when a was executing, x was stored on stack. now when a finished, a was removed along with x. but y still references a as closure. how it is able to when a was removed (thus removing x)
@@alexhyettdev what I meant is - when a inner function reference a variable from parent function, where is that parent function' variable stored ? assume variable is primitive so you would say on stack but when parent function returns the inner function to caller of parent function & parent function execution finishes, parent function is pop from call stack. but when later inner function returned earlier is called later, it still can print that referenced variable which was removed from stack earlier
"Whenever you run anything asynchronously, it's gonna get run in a different thread." This is a wrong statement , asynchronous operations can use the same thread.
hell yeah. idk how you did it but that finally made sense. i had to have heard the stack of books analogy before, but this is probably the first time seeing it played out with actual books imma have to watch this again
This makes me wish for a world where we threw out the ram middle man and just read straight from the ssd and only had to worry about a little bit a caching. Stuff like Intel optaine is getting kind of close to speeds and read/writes where this is possible, but I’m sure there are thousands of reasons why this couldn’t happen
Thank Alex, So in that case , then why I should know about the memory allocation if I can't able to assign.. There must be a reason pls help me understand..
These ideas were saved in my head as a sequence of words for the entirety of my undergrad. If 5 short minutes you managed to actually help me understand a huge gap in my understanding. Thank you so much.
You're welcome Michael, I am glad it helped.
@@alexhyettdev
public class Main
{
String s = "ABC";
public static void main(String[] args) {
Main obj = new Main() ;
System.out.println(obj.s);
}
}
in this above code String object is created in heap and also of class.
So 2 objects in heap.
But isn't the string object Abc resides inside class object in the heap?that's why we are calling it obj.s
Good video very in-depth
i feel the exact same way!! this random collection of words and statements now i feel like concrete concepts in my brain
@@alexhyettdev Quick question. You mentioned that when a pointer/ref in the stack is deleted, the value it points to dangles around the heap until the GC collects it, but what happens in a language like C++ there is not GC? Would that become a memory leak?
Alex, you made my day. I would call you one of the best instructors! Your explanations are flawless. You explain perfectly in context. For instance, where you explain why variables are not accessible outside the method.
Jake, you made my day! Thank you for the lovely comment. I am glad you found it helpful!
YOU ARE LITERALLY CAPABLE OF REPLACING 99 PERCENT OF TEACHERS WHO PATHETICALLY FAILED TO TEACH ME THIS CONCEPT. THE CLARITY WITH WHICH YOU JUST EXPLAINED IT SHOWS THE TRUE MASTERCLASS YOU ARE IN. I WISH I DINT WASTE MONEY IN COLLEGE WHEN PEOPLE LIKE YOU EXIST. LOVE YOU SIR ❤
Not gonna lie, i cant state enough how explanations like this can massively improve your understanding of why code works the way it does. Just learning to code is one thing, but understanding whats behind all of it and WHY whatever thing actually is happening, can definitly up your game. Im not a pro by any means, but i think stuff like this is very important.
The visual presentation also makes it way easier to follow and connect the concepts - so thx for that 😊
Thank you, I am glad you enjoyed the video. I find it helps with remembering everything as well. If you can understand something then it tends to stick in your mind a bit better.
This is one of the best programming related videos I have ever watched. It cleared up so much of my confusion in C++.
Thank you!
Thank you sir. Good Explanation.
Please, I wish you make a video on "Why in Java, Do Local Variables Used in Lambdas Have to Be Final or Effectively Final?" and please make the explanations at the memory level too, so we can understand all the mechanics behind it.
The static variables are supposed to be stored in the Data Segment not Stak or Heap. the video mentions that static variables are stored in the heap.
Reading a book right now that explains this concept rather poorly over 20 pages. You managed to grant me understanding in 5 minutes, and now I can continue reading past the chapter. Thank you, great explanation!
You’re welcome! I am glad I could help you understand it. Hopefully more fun than reading 20 pages of that book.
The best explanation/animation ever.
Thank you!
"Whenever you run anything asynchronously, it's gonna get run in a different thread."
This is a wrong statement , asynchronous operations can use the same thread.
Yeah I think his example only works for multiprocessing based parallelism? Single threaded asynchronous operations will still have one thread right?
Perfect, really good explanation. Thank you!
Finally a much simpler with actual sample code that explain the whole stack and heap stuff. Now I understand why and when OOM occurs in app, the usual suggestion is to increase heap size but said to be slow or when we do recursion recklessly we get stackoverflow.
Aren't static variables stored in the data segment? Not sure if any language stores static variables in the heap?
It seems to depend on the language. For C# they are stored in the heap from what i have read. C and C++ you right it is the data segment.
This video actually answered all my questions about how the stack and heap work together. Great explanation!
you speak so fast, I have to do it on .75
Insanely useful video, didn't think i'd learn that much in just under 6 minutes, thank you.
This is an excellent video about how the memory works, I love the last part about asynchronous methods. Thank you for this awesome content. I wish you could speak more about asynchronous functions. 😃
This explanation was exactly what I needed! thank you Alex
You’re welcome I am glad it helped!
While asynchronous methods can run on different threads, they do not necessarily have to. Aync execution can also involve single-threaded environments. E.g.: with event loops (JavaScript / Python's asyncio)
The analogy of a stack of books provided much needed clarity for me. I appreciate the video mate!
You’re welcome, I am glad it was helpful.
thanks dude
transition from a synthwave enlightened dim ambient to blazed fluorescent white graphics... x_X
I've been coding, and teaching code for the past 4 years. This video blew me away. Explained everything so well, and was incredibly easy to follow. Sorry, Alex, I will be stealing this! Amazing work, and you've got a new fan! Thank you!
Can you re-check this one? I think something is incorrect with global or static variables.
We basically have 4 segments: Stack, Heap, Code Segment, and Data Segment.
Global or static variables, including constants like `const int MAX_AGE = 99`, are not stored on the heap. They are typically stored in the Data segment of the memory, specifically in the initialized data section.
The Data segment is a part of the memory that contains static and global variables. These variables are allocated and initialized before the program starts executing. The initialized data section of the Data segment holds variables that have explicit initial values, such as the MAX_AGE constant in your example.
In C#, async methods that complete sync, before you await them, will not go onto the heap, hence the reason we have ValueTask now. However, if you use a ValueTask struct and it doesn’t complete sync, then you incur a hit of boxing, allocation, and deallocation (GC collect), which makes it a tiny bit more expensive than the regular Task class.
One more thing. If you cast any value type to an Interface type, it will go onto the heap, even if it’s a struct or value type.
Many thanks to your video, this UA-cam is valuable, so I read word by word carefully. And I find at 03:55, about the static variable, which is different from what you mentioned in your flvog (the link you provide in descriptions). In ur flvog, in para "where do static variable live", there you said static variables even if they are value types are not stored on the stack or the heap...need clarify? Thanks.
Thanks for spotting the discrepancy! I need to update my blog to make things clearer.
Basically it is an implementation detail. In C# static variables are part of the MethodTables on the "High Frequency Heap". Which is a special part of the Heap memory for static variables and internal data structures.
In C and C++ they are stored on the Data Segment, which is a special part of the memory for storing static variables and internal data structures.
:) Sound familiar?
If you look up Data Segment and High Frequency Heap they are both in the same place in memory. By the looks of things they are just slightly different implementations of the same thing.
There is an old article here that explains it in depth:
web.archive.org/web/20140724084944/msdn.microsoft.com/en-us/magazine/cc163791.aspx
Jon Skeet also has a good article on it as well:
jonskeet.uk/csharp/memory.html
@@alexhyettdev Thanks for your response and your UA-cam.
Asynchronous methods don't run on different threads. They run on a single thread but with a flexible event loop mechanism
Your videos are awesome and very clear.
Can't wait for a full CS playlist. Thanks for what you do for the community Alex.
Hello sir at 3:20 in the video you say that in must run times there is a garbage collector that will clean the memory from the stored memory location after it has finished execution. Not sure if you know but with in C and C++ language we do not have a garbage collector I was told. So in C and C++ we delete pointers manually after block execution. So, Actually C and C++ are not garbage collecting languages.
We 2x forward boring videos. But I needed to 0.5x slow down this video
I loved the explanation, just a small feedback you have tried to make the video stunning.
Since you sit in a dark room and you are showing code on white screen its really painful for the eyes. Also this effect of your video zooming in out its very annoying.
All the best and keep up with the good content
My jaw dropped when you explained what happens to variables declared in the stack, I never made the connection between this fact and the scope of variables, thank you soooo much !!!
Samee heree, I've never even thought of why we couldn't call variables from different scopes, i just took it for granted this opened my eyes
I'd be extremely weary of taking this for fact. It is up to the compiler to generate scoping rules, as far as I know. Look into it a bit more.
Really nice explanation but I have one doubt, I used to think that global variables are stored outside of both stack and heap in a dedicated area for global and static variables. Would be great if someone could clarify on that.
such a clear explanation couldn't get better thanks Alex
@4:23 what do you mean by the anonymous function is pushed on top of the stack and not have access to what previous level down? You mean even variables within main?
#amflearningbudoing
Gonzalez Ruth White Scott Lopez Charles
Such a precious channel!!! Instant sub from me 🍻🍻
Good video.
One question: In the case of results from asynchronous methods, once the asynchronous function completes, who cleans up the result in the heap that was left over by the async function?
Generally they will be cleaned up by the garbage collector in the same way other objects on the heap are.
@@alexhyettdev thanks for your response
I do not think so there is a case where global variables stored in heap
Great video, great explanation! Thanks
hey this is an excellent video! i'd never thought or read about the link between variable scope and memory. thank you so much!
Very good explanation, thank you.
Heap is the same as heap data structure for prioritizing values?
subbed! i was here @11.5K subscribers! will comment again WHEN you reach 100K.
Thank you! Fingers crossed!
This was not at all useful to me.
There's different uses of system memory. Program memory - a copy of the actual program in system memory, usually completely static. Execution memory - any allocated memory that could die at an unknown time (from the point of view of the OS) - the typical "heap". Local memory - value storage, exactly as you described it.
Then there's the actual hardware - filesystem storage, system memory, CPU cache, GPU cache...
Fair enough …
I did find the whole talk quite oversimplified and reflecting the behaviour in one programming language or possibly one particular class of languages.
C memory model is pretty much everywhere, so starting there isn't stupid
Wow this was an incredible series of topics, thank you!
Thanks, I’m glad you enjoyed it!
I wonder why we don’t have a heap stack. In theory, programs are hierarchical, at the top are all the values that live for the lifetime of the program. Below that, there are things that will exist for a shorter duration as different functions/methods are called. Eg in a web app, there are values and objects that are created to manage the web application, then for each request, there are values and objects created specifically for each request that don’t need to hang around after the request. And within each request, there are further subdivisions of lifetimes that don’t need to hand around for the full duration of the request. In theory, all the values and objects specific to the request could be put in its own heap, and on completion that heap gets cleaned up. Anything that should remain after the request would be on a different parent heap with a longer lifetime. The running program could keep statistics of the size of the heap required for different parts of the application. Maybe garbage collection already works this way though. But I don’t think so, eg with .net and the generational garbage collector. Maybe the programming language that have explicit lifetimes or ability to manually control allocations have this.
That's literally just a heap and a stack, but stuck together. I don't see the benefit or how that solves a problem. It might make a new problem though.
Resist the temptation to fix what isn't broken.
Thank you very much mate.
Clear : )
This video needs to be promoted higher on UA-cam. Anyone who wants to learn Rust should start from here before diving into the borrow checker.
Thank you. I am glad it is useful for people learning Rust as well. Some of the C# references might not be applicable but hopefully the rest is. I need to learn rust as well actually!
Can you recommend 2 or more books on memory and data structures?
Awesome video, very short and to point.
But where stack is? Is it in RAM or Hdd or in processors registers? Where physically it is?
Learning assembly will teach you this better than I can. It's a mixture of CPU registers that hold references to areas in RAM that represent the stack abstraction. The data lives in RAM but the CPU registers are key to understanding the flow I think.
Is this what a memory leak is? If something like c++ that doesn’t have garbage collection or something gets left on the heap is that memory leaks or is that something else?
Yes exactly, languages like C++ which don't have a garbage collector need the programmer to release the memory correctly. If they don't then memory stays allocated on the heap and can't be accessed by anything causing a memory leak.
Great explanation! Thank you! My only bit of feedback would be to stay on the graphic visualizations longer. The constant switching between the visualizations and the shot of you talking is a bit jarring and makes it harder to focus.
"In a previous video" you talked about value type and reference type... can we get a link to that? I found a playlist but this is the first video in it.. there is no previous video
It was very briefly here: ua-cam.com/video/pKFcVs2HibA/v-deo.html
thats lot of info, more than what i was looking for. 👍
thank you
Do you have any course, which includes all these valuable topics with animations
I have only started making courses recently. My first course on Solid came out 3 weeks ago: dometrain.com/course/from-zero-to-hero-solid-principles-for-csharp-developers/
Thank you for this explanation.
You do talk a bit fast.
But thanks nonetheless.
Thanks. Yes I think I have managed to slow down a bit in my newer videos.
You're great. Thanks
I just have one question about this, are the heap and the stack RAM? Does ROM have them too?
Yes Stack and Heap are stored in the RAM. ROM doesn't have a stack or heap as ROM is Read Only Memory. It is written once and can't be changed. It is typically used for low level code such as the BIOS. Although even that is usually stored on Electronically Erasable ROM (EEROM) so that it can be updated. All of the applications on your computer including the OS will use the RAM. Stack and Heap are just ways in which the memory is structured to store your application code.
Damn! I thought it's about neurology
It sometimes feels like you need to be a neurosurgeon to understand this stuff!
I've seen multiple videos of you now... you can explain the essence of things very well. It's a talent. Very good. Thank you!
A hidden gem !!! Thanks you so much, I understand it so much better now !!!!
I am glad it helped!
Really good video, but i had to watch it on 0.75 speed.
Thanks. Yes I have got a bit better with my pacing in my newer videos.
This is good. Have learned some things I could not know in a year.
That’s great I am glad you learned something from it. Thank you for commenting.
Low key asmr every time he says staKK
Amazing explanation, greetings from Chile
Thank you! Hi 👋 from UK 🇬🇧
great explanation thanks
3:01 small correction. A const is NOT allocated on the heap. In fact, it's embedded on the call site at compile time (in C#/F#/VB), the reference is removed (you can test this: create a const in another lib, reference and use it in your lib. Compile. Now update the const in the referenced lib and recompile, but do not recompile your lib. You'll see it did not change on the call site). What you probably want is readonly, which, in your example at 3:01, would then be allocated on the heap.
I can't put into words how helpful this video was. Thank you Alex!
So a heap is like a matrix?
How does garbage collection handle memory fragmentation? Is there a heap defrag utility?
Do you wipe the heap when a program ends? What is multiple programs / threads run concurrently?
Now I need to check the rest of your videos for answers.
Thank you for starting my journey.
Incredible. Even though I've been a professional developer for six years, I was having a crisis of confidence tonight because I've worked with languages where I never have to worry about this directly. I was asking myself, "Do I even know anything about computers if I don't know the difference between the stack and the heap?"
Five minutes and twenty-seven seconds later, I feel like I have a solid understanding of the difference and I'd be capable of talking about this intelligently. Thank you 🙏
I have been a developer for 12 years and I went through exactly the same thought process before making this video. I am really glad it helped you.
Same here just went through a training where some memory management stuff was covered and I felt like an imposter. This made it all make sense
suppose a function a returns another function b, that returned function b has reference to local variable x in a, now in stack when a was executing, x was stored on stack. now when a finished, a was removed along with x. but y still references a as closure. how it is able to when a was removed (thus removing x)
I am not sure I get your example. Maybe one to try and work out.
@@alexhyettdev what I meant is - when a inner function reference a variable from parent function, where is that parent function' variable stored ? assume variable is primitive so you would say on stack but when parent function returns the inner function to caller of parent function & parent function execution finishes, parent function is pop from call stack. but when later inner function returned earlier is called later, it still can print that referenced variable which was removed from stack earlier
Thank you very much i was not able to understand this concept even after reading and watching a lot of videos now i have a good understanding of this
That’s great! I am glad I helped.
@@alexhyettdev if possible can you please explain the anonymous function part i didn't get it
I thought async was on the same thread
await and async use Tasks not Threads, so you're right, it's technically using the same thread.
"Whenever you run anything asynchronously, it's gonna get run in a different thread."
This is a wrong statement , asynchronous operations can use the same thread.
straight to the point 💯
excellent explanation but little bit fast :)
Thanks. My newer videos are a bit slower paced. Takes a bit of practice!
Great explanation!
Really great video! This helped so much
Thank you I appreciate the kind words. I am glad it was helpful.
Wow. Mind = blown.
Can't find the reference type and value type video. Can you please share the link/ Thanks!
It was very briefly here: ua-cam.com/video/pKFcVs2HibA/v-deo.html
I probably need to do a separate video on them to be honest.
@@alexhyettdev I like the way you explain the concepts!! Would to love see the a video about pass by value and pass by reference with more examples.
Finally I understand the difference in few words and short time... keep doing videos like this
Loved the garbage collector animation. Very nice and funny
Excellent explainer and graphics THX
You’re welcome, I am glad you like it.
Excellent explanation. Thank you so much.
hell yeah. idk how you did it but that finally made sense. i had to have heard the stack of books analogy before, but this is probably the first time seeing it played out with actual books
imma have to watch this again
Very well explained. Thank you!
Thank you, I am glad you liked it!
Cool Stack
This makes me wish for a world where we threw out the ram middle man and just read straight from the ssd and only had to worry about a little bit a caching. Stuff like Intel optaine is getting kind of close to speeds and read/writes where this is possible, but I’m sure there are thousands of reasons why this couldn’t happen
Great video!
Amazing
very nice video
A nice and concise explanation . Wishing you all the best for better reach of your subsequent tutorials so a lot from community would benefit
How could I assign which data must store in which memory?
You can't. It is decided by the application runtime.
Thank Alex,
So in that case , then why I should know about the memory allocation if I can't able to assign..
There must be a reason pls help me understand..
Great Vid
Comment