JavaScript Under The Hood [4] - Memory Storage

[@ngolelawsonmbwoge3647]

I think this is the first time I truly understood, when they say objects are passed by reference, from the diagrams you showed. And visualizing the heap memory storing objects, functions and arrays and stacks storing primitive data types, is just gold! It makes it way clearer to understand! Thank you so much, sir Brad!

[@umamaheshmeka1032]

The Voice - which motivates developers to go to any extent to learn !!! I really love your teaching 💝💝💝

[@PRAHLADSAHU-pk4fd]

I like the way he admitted he doesn't know about memories much and still gave the relevant info with great explanation.

[@vinaypatil8009]

That heap memory explanation with diagram is on point perfect. Thanks for your hard work sir.

[@kosmarjus]

Ohhh man this took me so long to figure out. I was so mad why my initial object changed every time I recalculated some values. Thank you for shedding some light on the subject.

[@jhmesseroux]

more videos like this , love it Brad , i learned something new

[@darkmojojojo]

Keep going with these videos. It's definitely helping with understanding why JS behaves the way it does for me.

[@devbrothonath9396]

2nd time hearing about stack and heap and it's set in my mind. This was so simple, it blew me away.

[@pablojoyce]

This is a great series! Thanks. You mentioned revamping the modern JavaScript from the beginning course. I’d love to know when that is going to happen, Brad. I love your teaching style and almost signed up last week but was put off by the age. Considered other more recent courses but would definitely take yours if updated.

[@godfreyndiritu9062]

Imagine all that knowledge in 12 minutes, how much more helpful if it was an hour or so? Thanks Brad

[@darkmojojojo]

Personally I like these bite-sized videos. They help me with understanding basic concepts without having too much information thrown at me at the same time.

[@Retrofire-47]

@@darkmojojojo pots and pans, stranger.

[@lathamanoharan642]

Thanks for this series Brad. It was very helpful for me to understand some of the basics of why javascript works this way

[@WendimuSitotaw]

I'm really digging this series!

[@bevedel]

Waiting for more videos from you. Thank you for this great serie.

[@alexiscostoulas]

maybe the best and most clear explanation on this topic !!

[@elyoaprogrammer]

Execellent series..I enjoyed it!..Thanks Brad !

[@genrum4803]

Love this series, very helpful for beginners.

[@eillioniscreating]

Please make more video ! I love your videos.

[@ahmad-murery]

7:34 I whish 40 but we'll say 44 😥 so, enjoy it while you're there, Thanks Brad,

[@thisweblabvideos]

Amazing video. Well explained and important. Thanks

[@josephwong2832]

Wow! Finally I understand it now. Thanks Brad

[@bossmohd]

Great video, although I came in looking for something else but this was informative. What I was looking for is recommendations for memory management. For example, is it bad to declare variables or should we try to minimize it. For example should I do const result = someFunction() and then return result, or return someFunction(). Is this more efficient? What are the tools that can help us measure performancece in node? Are async/await consuming more memory than sync functions?

[@xkwantified]

Excellent series👍!

[@gunarcom]

This is a strong video. Good work my friend!

[@nikhilmandaliya]

Thank you for this series, your explanation makes advance concepts easy to understand. But I have one question, if primitive variables are stored in stack, is this same as call stack? If yes, then that variables should be removed when function completes execution. So how a function can access that variable in terms of closures?

[@drippindamnfaucet3309]

Nice Xplanation!!!!

[@mirkafarkasova2425]

Great video! Had no idea it works like this. In what case would I use this tho?

[@mattkeg]

in the first example from 4:35 to 6:47 is the 'stack' the global execution context?

[@ScriptRaccoon]

Shoutout to Github Copilot who always knew what Brad wanted to type next :-O

[@G.Lomidze]

Thank you for series. Please one question. On 8.17 min which extension create a line on the variable which is not use now? Which extension is this

[@rutvijdoshi9664]

Great video. Please create video series on React under the hood.

[@sourandbitter3062]

Love the new intro

[@tamboleo]

Newby question here, how is he having the values directly on the console without refreshing the code every time? I saw this behavior on Angular but didn't know you could get real time updates on JS as well, is he using an extension or something ?

[@moqusi24]

Thank you for the explanation

[@jonp9511]

Very helpful

[@yoshreimi]

wow thank you so much for creating this content for free

[@DanzzyTechWorld]

This explains mutability well

[@josheppinette7381]

Primitive values are not stored on the stack. They are stored on the heap. The only exception being small integeres (

[@deathangel908]

Is stack can't handle variables of variable size, how comes when you change a string variable it still resides on the same spot in the stack?

[@nithinraj342]

U r a good teacher. Can u do video on how nestjs project architecture need to be.

[@buddhaburrito]

11:10 I wonder how he auto complete those lines? Did he store it somewhere? What vscode extension was it?

[@ScriptRaccoon]

It's Github Copilot.

[@buddhaburrito]

@@ScriptRaccoon Thank you!

[@mtxar]

great content dude!!

[@thewild123]

Hey Brad, thanks for the tutorial. I wonder if these diagrams help professional developers visualize how memory is occupied in their apps? I don’t really consider myself a professional but I did study memory management and memory allocation strategies by operating systems. I think it’d be better for myself and more advanced developers to study how JavaScript engine allocates memory on a much more lower level.

[@nicogarcia7302]

Great video Brad!! I have a doubt tough, when you you reassign newName, shouldn't it still be in memory and the engine allocates memory for a new string?

[@legalcoffee5315]

So helpful 🎉thanks!

[@prudhvichinnam1488]

Do series on react under the hood

[@anandstephan6020]

please make more video of javascript core concept

[@bhuvandwarasila]

fire brother

[@mahdikamran8061]

Thank you.

[@dasuntheekshana3433]

nice work thank y0u

[@Red_Coder]

Is there course Js under hood

[@georgenonis5967]

Not sure why but I cant find objects in the snapshot. Great video anyways and great explanation as always

[@developersharif]

Love from Bangladesh ♥

[@MgelikaXevi]

for algo, great series!

[@eboum4273]

Thanks

[@sujaigorai7752]

Everything in javascript is stored in heap memory

[@k.ksharma4457]

awesome👍👏

[@lilyscarlet2584]

just use arena allocators in c if you want memory safety. no gc or raii needed. that way you dont have so many independent lifetimes. thats the real problem. all gc does is kick the can down the road.

[@najeemfasil5199]

great 😇

[@mecreature]

😍😍😍😍😍

[@DmitriyMalayevProfile]

Primitive Types: BeBUNSS