Running Go with GOGC=off, and an idempotency race nobody tests

The liveliest thread of the day asks whether a long-running Go program can realistically live with GOGC=off and a C-style allocation discipline, which is the kind of question that sounds unhinged until you actually try to answer it. Alongside it, a writeup on idempotency keys picks apart the check-then-act race that quietly breaks retry logic in payment flows, and part three of the distributed-systems-without-Raft series continues its slow campaign against consensus orthodoxy. Elsewhere, TinyGo cut espflasher v0.7.0 for the ESP32 crowd, and someone is writing a book on game programming in Go with Ebitengine, which feels like a healthy sign for the ecosystem's weirder corners.