Podd: Fallthrough

Tools We Love

3 mars 2025 | 114 min

Ghosttying Go

24 februari 2025 | 95 min

What's a terminal? Why is it being emulated? On this week's episode, Matt and Kris are joined by Mitchell Hashimoto to discuss his newest project Ghostty, the Zig programming language, thoughts and feelings about Go, and more. As always, catch some Unpopular Opinions at the end of the episode.

Want to hear even more from Mitchell? This episode features bonus content for our Fallthrough Fan and above subscribers! Become a supporter and enjoy bonus content and higher quality audio today, and additional perks and benefits when we add them in the future.

Thanks for tuning in and happy listening!

Notes & Links:

How to reset the terminal in Ghostty (from 04:41)
- Ghostty reset keybinding
Sunsetting Cursed Terminal Emulation (from 18:22)
XTGETTCAP in Ghostty (from 23:31)
ncurses terminfo database (from 25:14)
Gnome VTE (from 36:55)
Mongoose embedded web server (from 52:28)
libuv (from 52:40)
freetype (from 52:44)
HarfBuzz (from 52:45)
Pixman (from 52:48)
libxev (from 52:58)
z2d (from 53:01)
Scripto Continua (from 01:25:26)

Chapters:

(00:05) - Intro
(00:39) - Become a subscriber: https://fallthrough.fm/subscribe
(01:52) - What is Ghostty?
(03:47) - Consequences of cat'ing binaries
(04:43) - Ghostty's journey to release
(06:47) - Ghostty's team structure
(08:22) - What terminal are we using?
(09:03) - Ghostty's Dev Tools
(14:53) - What are escape sequences?
(16:57) - What are terminal emulators emulating?
(19:50) - The ossification of SSH & Terminfo
(27:26) - Ghostty Terminfo workaround
(28:38) - Shell in the Ghostty
(34:44) - libghostty
(38:59) - The most difficult part in implementing Ghostty
(42:35) - Why Zig?
(46:41) - How to build with Zig
(55:35) - The Zig Standard Library
(59:00) - Social feedback creates bleh languages
(01:02:52) - Go's place in the modern world
(01:11:56) - On handling feedback
(01:19:45) - Join the Ghostty development community
(01:21:35) - Mitchell's thoughts on GitHub (subscriber only)
(01:23:02) - Mitchell's Unpop
(01:24:21) - Matt's Unpop
(01:26:37) - Kris' Duolingo Streak
(01:29:29) - Kris' Unpop
(01:33:25) - Outro

Hosts

Socials:

Patching Problems with Persnickety Proxies Purveyed by Paternalistic Princes

17 februari 2025 | 127 min

A recent Ars Technica article outlined a backdoor in the Go Module Mirror. Even though it's framed as a backdoor, and potentially a vulnerability, it's actually an exploit of a design choice designers of the module mirror made. Kris is joined by Matthew, Dylan, and guest host Jamie Tanna, to discuss this vulnerability-but-actually-feature, the implications for the Go community, and the wider reasons why something like this happened. We go on a journey through the history of modules, the Go community, and a whole lot more. We know this is a long one but we're sure you'll love it! Have thoughts? Reach out to us on social media and let us hear them!

Thanks for tuning in and happy listening!

Notes & Links:

Chapters:

(00:05) - Intro
(01:38) - Introducing Jamie Tanna
(02:21) - The vulnerability that's actually a feature
(04:53) - The Go Module Mirror
(14:02) - Paternalism
(21:14) - What are vanity URLs?
(23:02) - Not just the official Go Module Mirror
(27:58) - Unforgiving Module Proxies
(29:23) - #BringBackGOPATH
(29:36) - Tags are mutable
(33:44) - What does a version mean?
(35:10) - Jamie's Hot Take
(38:20) - The Trails and Tribulations of Modules
(42:03) - It's humans!
(44:40) - How might we fix this?
(49:12) - Is it too easy to fetch dependencies?
(52:25) - Decentralized versus Centralized
(57:24) - A Proxy is not an Origin
(01:03:14) - Can we revalidate?
(01:05:14) - I can't believe it's not SemVer!
(01:06:34) - Analogy Time, featuring The Web!
(01:09:25) - Is this a problem elsewhere?
(01:12:20) - The tooling should be better
(01:16:47) - The Community that was
(01:23:06) - Matthew's Is Go Dead? Perspective
(01:23:59) - Jamie's Is Go Dead? Perspective
(01:25:19) - What does Dead mean?
(01:28:23) - Go should be able to do more
(01:31:22) - Go as an identity
(01:32:33) - Some added nuance
(01:39:18) - A difference in leadership
(01:43:03) - A lack of inclusion
(01:57:34) - Blame the system, not the person
(02:03:00) - Outro

Hosts

Socials:

What's New In Go 1.24?

10 februari 2025 | 66 min

Navigating A Career In Tech

3 februari 2025 | 86 min

An Exploration of Complexity

27 januari 2025 | 100 min

Modern software development feels so complex. In this episode, Ian Wester-Lopshire is joined by Kris Brandow, Matthew Sanabria, and Angelica Hill to discuss complexity. They propose hypotheses for the root cause of complexity, explore the ways complexity affects our technology and organizations, and ponder if artificial intelligence can aid us in reducing complexity. As always, we've got some great unpopular opinions at the end.

As always thanks for tuning in and happy listening!

This episode is a pilot for a planned mini-series on complexity. We'd like to explore complexity deeper by having conversations with and interviewing a diverse set of people. Do you have thoughts about complexity, know someone who thinks deeply about this topic, or have something you'd like to add? Reach out to us on social media and let us know!

Notes & Links:

Chapters:

(00:00) - Intro
(00:31) - How are we doing?
(01:24) - Where did complexity come from?
(02:53) - Ian's Hypothesis
(07:00) - Kris' (Hot Take) Hypothesis
(14:38) - FAANG & Engineering Excellence
(19:21) - Do better practices lead to complexity?
(24:02) - The Cloud's enablement of complexity
(24:39) - Some of the complexity is worth it
(26:01) - Systems become more complex over time
(27:33) - Moving Faster & Thinking Less
(31:18) - Accidental complexity
(31:47) - Where else does complexity surface?
(32:03) - Human Organizations & Trading Complexities
(37:46) - Documenting Decisions
(38:20) - Hypoethsis: Bad information organization is the root of complexity
(49:01) - Can AI be our librarian?
(54:39) - Search is not a text box
(55:57) - Machine learning for indexing
(01:00:17) - Can AI write our code?
(01:05:44) - Easy & Hard Learning
(01:12:27) - Hypothesis: mixed and unclear terminology
(01:14:46) - Concise Hyopthesis of Complexity
(01:18:05) - Letters by mail?!
(01:18:56) - Unpopular Opinions
(01:19:14) - Matthew's Unpop
(01:23:10) - Ian's Unpop
(01:28:30) - Kris' Unpop
(01:35:47) - Fallthrough & CPU.fm
(01:37:39) - Complexity Mini-Series
(01:38:26) - Outro

Hosts

Socials:

Do We Think You Should Learn To Code?

20 januari 2025 | 99 min

For years we've been told that everyone needs to learn to code. As career software people, what are our thoughts on this? Should you learn to code? Is coding the right career for you? In this first episode of a two part series, the panel discusses how they learned to code, whether they think everyone should learn to code, and of course they offer up some unpopular opinions.

And if you're thinking, "I already know how to code", don't worry, this episode contains valuable advice for you as well.

As always thanks for tuning in and happy listening!

Notes & Links:

Ben Eater's YouTube Channel (from 53:00)
John Carmack's Fast Inverse Square Root (from 1:01:47)
- This is actually from Quake, not Doom.
Change Interviews #581 It's Not Always DNS (from 1:04:15)

Chapters:

(00:00) - Intro
(01:33) - How're we doing?
(04:41) - Why did we learn to code?
(06:10) - Why Kris learned to code
(07:44) - Why Ian learned to code
(08:54) - Why Dylan learned to code
(10:36) - Why Matthew learned to code
(14:22) - Computer Assembly Not Required
(16:51) - Tangent: Why Are USB-C Cables?
(17:36) - Should you focus on a specific language?
(22:45) - Do you want to solve problems?
(24:53) - Coding & Woodworking
(27:09) - Curiosity & Itches that need scratching
(31:07) - What do we mean when we say "code"?
(32:34) - You should learn Excel
(39:35) - Coding Is Configuring Computers
(43:32) - Discrete Math, Not Binary
(47:03) - Learn the low level stuff... eventually
(53:42) - The desire to learn
(57:41) - Sidequest: Networking
(01:05:52) - Learning Design & Being Load Bearing
(01:12:10) - Continual Learning
(01:14:33) - What of AI and Automation?
(01:21:49) - Share What You Learn
(01:24:24) - Should You Learn To Code?
(01:24:57) - Teaser: Episode 5 - Is Coding The Career For You?
(01:26:02) - Unpopular Opinions
(01:26:08) - Matthew's Unpop
(01:28:51) - Ian's Unpop
(01:29:29) - Dylan's Unpop
(01:33:52) - Kris' Unpop
(01:36:50) - Tangent: Chopper?
(01:37:27) - Outro

Hosts

Socials:

The Gems & Warts of Go

13 januari 2025 | 117 min

Gems are the things we love, and warts are the things we don't. On today's episode, Kris is joined by the hosting panel of Ian, Matt, and Dylan and they are talking about the gems and warts of Go. From defer, to net/http, to vanity URLs, to modules, we cover around 30 topics! To prevent our listeners/viewers from returning an E_TOO_MANY_UNPOPS error, we didn't include the Unpopular Opinions segment (there are plenty throughout the episode). We hope you enjoy this tangent filled episode. Have a gem or wart you agree/disagree with or think we missed a few? Let us know on social media or in the comments!

Thank you so much for listening. Happy listening!

Notes & Links:

Chandler Carruth's CPPcon talk (from 40:44)
Go x/tools/guru (from 43:36)
- Since deprecated, however this functionality is included in gopls.
go/analysis (from 47:19)
go/x/tools/cmd/eg (from 1:47:25)
- go/x/tools/refactor/eg
- eg documentation

Chapters:

(00:00) - Intro
(00:31) - Introductions
(05:07) - Gem#1: net/http
(07:37) - Gem#2: defer (gem)
(09:36) - PEBKAC (tangent)
(11:36) - Gem#3: if err != nil (gem)
(16:09) - Gem#4: testing included (gem)
(19:13) - Gem#5: struct field tags (gem)
(21:57) - Gem#6: reflect & unsafe (gem)
(24:35) - Gem#7: sync/atomic (gem)
(24:54) - Gem#8: io as composeable interfaces (gem)
(25:32) - Gem#9: No inheritance (gem)
(31:20) - Gem#10: Vanity URLs (gem)
(34:33) - Gem#11: single for loop (gem)
(37:08) - Gem#12: pprof (gem)
(38:25) - Gem#13: security by default (gem)
(40:01) - Gem#14: fast compiler times (gem)
(41:16) - Gem#15: go/ast & go/* packages (gem)
(42:05) - Gem#16: implicit interfaces (gem)
(42:38) - Wart#1: implicit interfaces (wart)
(48:37) - Wart#2: slice tricks (wart)
(54:10) - Wart#3: lack of method overloads (wart)
(56:57) - Wart#4: covariance for array parameters (wart)
(59:38) - Wart#5: encoding/json marshalling unexported fields (wart)
(01:01:27) - Wart#6: encoding/json marshalling errors (wart)
(01:02:31) - Wart#7: single letter variable names (wart)
(01:08:45) - Wart#8: iota (wart)
(01:16:09) - Wart#9: map operations (wart)
(01:18:23) - Gem#17: structs as map keys (gem)
(01:20:04) - Wart#10: main function signature (wart)
(01:23:35) - Gem/Wart#1: channels (gem & wart)
(01:30:38) - Wart#11: range loop variables (wart)
(01:34:31) - Wart#12: no standard build system (wart)
(01:38:09) - Wart#13: modules (wart)
(01:53:18) - Outro

Hosts

Socials:

War Stories

6 januari 2025 | 73 min

Falling Through: A New Perspective

16 december 2024 | 50 min

Falling Through: The Trailer

3 december 2024 | 8 min

Fallthrough

A deep and nuanced conversational podcast focused on technology, software, and computing.

Om podden

Avsnitt

Tools We Love

Ghosttying Go

Patching Problems with Persnickety Proxies Purveyed by Paternalistic Princes

What's New In Go 1.24?

Navigating A Career In Tech

An Exploration of Complexity

Do We Think You Should Learn To Code?

The Gems & Warts of Go

War Stories

Falling Through: A New Perspective

Falling Through: The Trailer