Understanding reading all available things from a Go channel (with a timeout)

Gateway pattern for external service calls

No matter which language you’re writing your service in, it’s generally a good idea to separate your external dependencies from your business-domain logic. Let’s say your order service needs to make an RPC call to an external payment service like Stripe when a c...

Races and memory leaks

#​564 — July 30, 2025 Read the Web Version Go Weekly Hunting a Memory Leak — Go has a fantastic runtime and garbage collection but that doesn't mean Go apps are immune to memory leaks. Jason, of the DoltHub team, shares the tale of d...

Microsoft build of Go 1.25 crypto backend changes

Starting with Go 1.25, the Microsoft build of Go will use system-provided crypto by default to align with Microsoft's internal cryptography strategy and compliance policies. The post Microsoft build of Go 1.25 crypto backend changes appeared first on Microsoft for Go Developers.

Mostly stopping GNU Emacs from de-iconifying itself when it feels like it

Getting decent error reports in Bash when you're using 'set -e'

Swiss Tables are a big plus

#​563 — July 23, 2025 Read the Web Version Go Weekly How Go 1.24's Swiss Tables 'Saved Us Hundreds of Gigabytes' — A look at how the new ‘Swiss Tables’ implementation in Go 1.24 helped reduce memory usage in a large in-memory map...

I'm on Fallthrough: Versioning: We Did It To Ourselves

Last week I joined Kris Brandow, Matthew Sanabria and Steve Klabnik on the Fallthrough podcast to talk about versioning. This was a fun episode - some really interesting threads, tangents, I felt I was much better than I felt I was last week, and I'm amazed that we didn't even go...

Building GoReleaser: from shell script to paid product

In this post, I want to share the history behind GoReleaser, how we got here, lessons I’ve learned along the way, and what’s ahead.

Building GoReleaser: from shell script to paid product

In this post, I want to share the history behind GoReleaser, how we got here, lessons I’ve learned along the way, and what’s ahead.