What's up with Go's error handling?

Duarte O.Carmo asks Ian Lopshire & Johnny Boursiquot about Go's error handling on the "Go Time" podcast. Full audio 👉 gotime.fm/308
Subscribe for more! 👇
Apple: gotime.fm/apple
Spotify: gotime.fm/spotify
Android: gotime.fm/android
Overcast: gotime.fm/overcast
Email: gotime.fm/email
Twitter: / gotimefm
Mastodon: changelog.social/@gotime
#podcast #golang #software #programming #softwareengineering

[@krumbergify]

if err != nil shows where things can go wrong and the programmer is forced to make a choice of how to handle it.
Let’s say that a function handles a list of incoming requests. What happens if the handling of one item fails? Should it just be skipped or is the combined result dependent on that each item has been processed successfully? Languages with exceptions lets you ignore those decisions and it leads to sloppy and broken systems.