Video series · 2 parts
How Go decides whether data lives on the stack or the heap, and how its garbage collector manages and is tuned for heap memory.

I break down how Go manages memory under the hood: the stack, the heap, and the escape analysis rules the compiler uses to decide where variables live. I explain why stack memory is automatically managed, LIFO, and…

I explain how Go's garbage collector manages heap memory, covering its non-generational, concurrent, tricolor mark-and-sweep design. I walk through why Go skips generational collection: the compiler keeps most values…


Dude, you’re at the bottom of my landing page.
Just book a call already if you’re that interested.
You scrolled all the way here.