Read/Write/Nil with Michael Knyszek and Michael Pratt
Please read important erratum at end of these notes!
Astute listeners will notice that this is the first episode in over a year. I recorded not one but two awesome interviews...and then failed to edit and publish them. Guilt over this haunted me. I have finally accepted I must declare moral bankruptcy on this front to be able to continue the podcast; I apologize. (I may yet bring those episodes back to life, but I will no longer block on them.)
In this episode, Michael, Michael, and I discuss an awesome debugging adventure deep in the Go runtime and linux kernel.
Links:
* Go issue: https://github.com/golang/go/issues/73581
* Metastable Failures in Distributed Systems: https://sigops.org/s/conferences/hotos/2021/papers/hotos21-s11-bronson.pdf
* Sponsor: https://sketch.dev/
Erratum:
I described elided nil checks as working by mapping the page at 0x0 as read only. In fact, it is unmapped, so that reads will also fault. Silly me.
Astute listeners will notice that this is the first episode in over a year. I recorded not one but two awesome interviews...and then failed to edit and publish them. Guilt over this haunted me. I have finally accepted I must declare moral bankruptcy on this front to be able to continue the podcast; I apologize. (I may yet bring those episodes back to life, but I will no longer block on them.)
In this episode, Michael, Michael, and I discuss an awesome debugging adventure deep in the Go runtime and linux kernel.
Links:
* Go issue: https://github.com/golang/go/issues/73581
* Metastable Failures in Distributed Systems: https://sigops.org/s/conferences/hotos/2021/papers/hotos21-s11-bronson.pdf
* Sponsor: https://sketch.dev/
Erratum:
I described elided nil checks as working by mapping the page at 0x0 as read only. In fact, it is unmapped, so that reads will also fault. Silly me.
Creators and Guests
