~golangweekly | Issue 550 - Some signal boosting for Go (8)

Using Signals with Go — Signals are asynchronous messages sent to processes to notify them of events like interrupts, crashes or termination, or to trigger certain behaviors. Most languages let you catch signals and act upon them, such as for shutting down a program gracefully, and Go is no exception.

Complete Go for Professional Developers — Craft production-grade APIs with Go, the language trusted by tech giants! Connect to Postgres, implement auth, and write tests that matter. Taught by a Twitch ML engineer who solves real problems with Go daily.

Fuzzing Go Binaries with LibAFL — Built upon the Rust-powered LibAFL fuzzing library, GoLibAFL brings ‘state-of-the-art fuzzing techniques’ to Go developers. This post compares it to existing solutions, shows off some examples, and digs into how they tailored LibAFL for Go use cases.

sync.Pool is Not a Silver Bullet — sync.Pool can reduce allocations and GC pressure, but it’s not a drop-in solution for every case. Jens looks at where pooling shines (predictable, short-lived objects) and when it can backfire.

Hoard of the Rings: Extracting Data From a Cheap Activity Tracker — Tony picked up a cheap activity tracking (heartrate, steps, etc.) ring and figured out how to use TinyGo to read its outputs. A fun yet practical use for TinyGo!

Mockery v3: Create Mock Implementations of Interfaces — With the very bold claim of Mockery v3 being able to make “obsolete all other interface-based code generation frameworks” in the Go world, the author has a good go at explaining why. If you’d rather just see the facts and give it a go, the homepage is a good place to start.

Bufstream: Robust Streaming for gRPC — Meet a cloud-first Kafka implementation custom-built for go gRPC streams. Plus, Bufstream is Jepsen‑tested.

Vite Backend Integration for Go — A way to integrate a Vite-based frontend with a Go-based backend app.