Golang pointers explained, once and for all

[@santiagosaavedra3724]

It was easy to understand because of the graphical content. Having stack and heap graphs along with the code helped me associate those two. Thank you for the video.

[@bachdx2812]

awesome video ! we need more of this kind of content on youtube !!! great work !

[@ansidhe]

The key thing to grok is: & = „address of” * = „value at” (of course apart from the * when used to declare a pointer variable 😉) Great animations BTW! 👍🏼🤩

[@fagnersales532]

Just started learning Go and I'm amazed that I could learn about Pointers in just 13 minutes. Amazing, never could really understand the idea of it in other languages, but did with easy with your explanation.

[@mxmlkzdh]

Jamie these videos are fantastic! Please don't stop making them. Thank you.

[@raypamber]

That's such a useful information in 13 minutes thank you so much for the content

[@juanjoivars3254]

Outstanding explanation, thank you for taking your time. I love the graphics shown, it helps a lot of 👍

[@gerinsz]

Thank you for re-uploading this video. I thought it was going to be gone forever after your previous channel.

[@thmater-x9786]

bless the youtube algorithm for this video just perfect

[@ll931217]

Just started learning golang after programming in python and javascript for over 6 years. I didn't study CS only IT, so all of this deep level stuff are very new to me, your explanation is super clear, I would recommend this video to people that are also starting out in golang

[@emmm_4465]

Right? This is a totally new paradigm for me also with JS background so super interesting. Think I wanna learn go

[@hendrywilliam]

@@emmm_4465 same thing for me, coming from typescript and learn go, and find out go is interesting to play with, also solved some leetcodes using go, it was fun experience.

[@KyleHarrington]

Diagrams on point (get it??). Seriously this channel is a goldmine

[@rkalpeshk]

Very good and clear explanation. Thank you for sharing the knowledge.

[@dab500]

Thanks for this video! You explained it very well. I tried a couple videos and I still couldn't get it till this video. Subscribed!

[@keen2461]

Excellent explanation! Thanks.

[@hameldesai4756]

Bless this video

[@pache5702]

Great video, I just have a bit of experience with C and this was easy to follow:)

[@mujibulhaquetanim]

Your explanation was spot-on, clarifying all the confusing parts, especially the puzzling matter of returning addresses versus copies. And your voice? It's soothing to the mind! Many thanks!

[@kmilorestre5223]

Just the day after I start learning Go, thanks!!

[@ayato7429]

Hey, your explanation was really really good! I will look into more videos of yours :)

[@viththagan3547]

Great Explanation.

[@romarioteixeira9567]

I recently started learning Go and will definitely keep an eye on this channel! Such a nice explanation

[@haroonalbar2725]

Thanks. really good explanation.👏

[@JigangLi-x3z]

Nice Explanation. I know there were a long history of debate about "Passing as reference" and "Passing as value". The immunity is a another good angle to think this problem. Thanks so much. The animation is super clear.

[@larenlarry5773]

This channel deserves more subs, gj Jamie

[@yogendra591]

Really helpful explanation! Thanks

[@bbcoolg100]

Really well explained! Amazing job!!! Thank you!!!

[@tz8904]

great video, great animation. thanks

[@AdiKSingh19xx]

Extremely helpful 😊

[@jigarn]

Nice and easy explanation, Thank you

[@davisbento]

Awesome explanation. Thanks!!

[@adardev-po2rg]

Hi Jamie, Please create a video on Garbage Collector algorithms.

[@Cyandog]

Hi! Really great job in the concise explanation! Got a like and new sub! One quick question though: Is the heap used when returning normal values as well or just for pointers? Does that heap allocation process happen everytime a function returns? Thank you in advance!

[@vaeris]

Normally a copy of your returned variable will be returned to the calling frame on the stack.

[@muhamadasif2802]

Nice

[@ProgrammingRainbow]

In Go *int is 2 tokens as in * int. The space is optional. I was also wondering if this subject is better suited to C instead of Go or, better yet, Forth or Assembly. Also, variable names get stripped when compiling normally. It's just address and type.

[@uipath234]

Please make videos on concurrency

[@925082]

Excellent explanation. May i know how did you make animation and show variable in box and lines what software or things?

[@erenyeager655]

canva

[@imranaalam]

interface, context, structs and functions plz

[@codelinx]

This isn’t the original channel…

[@darlymettmicheli2204]

what is the original?

[@nguyen_tim]

I think she got rid of it or renamed it. She has a channel dedicated to game dev though, youtube.com/@jamie_dev?si=VKI6v-HnKCFXY9Eo

[@ntkidding]

I been working with Go for so many years and, even knowing this stuff, is always good to refresh the mind. I have a question that might be due to not being a native, but I guess you said that we should use pointers for better usage of memory but this video proves different: kzbin.info/www/bejne/f4Sym3aspbOcj6M . Any opinion?

[@whiteingale]

I am going tos leep. Goodbye. see you