A deep dive into Go's stack

A technical dive into how the Go stack works and why we as programmers should care.

Leave us a comment

Changelog++ members save 6 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

• Tailscale – Simple, secure networks for teams of any scale. Built on WireGuard.
• Changelog News – A podcast+newsletter combo that’s brief, entertaining & always on-point. Subscribe today.
• Fastly – Our bandwidth partner. Fastly powers fast, secure, and scalable digital experiences. Move beyond your content delivery network to their powerful edge cloud platform. Learn more at fastly.com
• Fly.io – The home of Changelog.com — Deploy your apps and databases close to your users. In minutes you can run your Ruby, Go, Node, Deno, Python, or Elixir app (and databases!) all over the world. No ops required. Learn more at fly.io/changelog and check out the speedrun in their docs.

Featuring:

• Yarden Laifenfeld – Mastodon, Twitter, GitHub
• David Chase – Mastodon, Twitter, GitHub
• Mat Ryer – Twitter, GitHub, LinkedIn, Website
• Kris Brandow – Twitter, GitHub

Show Notes:

Something missing or broken? PRs welcome!

Timestamps:

(00:00) - It's Go Time!
(00:35) - Sponsor: Tailscale
(04:12) - Meeting our guests
(05:45) - Growing lilies
(10:05) - Starting at the basics
(14:13) - Sponsor: Changelog News
(15:23) - When does the stack shrink
(17:59) - Working backwards with memory
(23:38) - Can you be good enough?
(35:59) - The stack vs the heap
(43:10) - When to care about the heap
(56:26) - Measure first, optimize after
(1:00:53) - Unpopular opinions!
(1:01:10) - Yarden's unpop
(1:05:08) - David's unpop
(1:10:24) - Wrapping up
(1:11:30) - Outro

Episode source