Topic: Go

The Go runtime isn't aware if it runs inside a container under the resource constraints (CPU or memory). A mismatch in what the application thinks is has, and what the OS allows to use, can lead to the poor performance of the application after the unexpected throttling.

My personal list of "top conference talks", I keep referring back to, even after years of working with Go.

Every time I sketch an HTTP API in Go, I wrap the code of request handlers around these small but very convenient bits.

Lately, I’ve learned, jsonb prohibits insertion of a valid JSON string if the string contains NULL (U+0000) character.

profefe-collector, the main component of profefe, a system for continuous profiling, receives profiling data from an application and persists the data in the collector's storage. But why waiting for the data to be pushed instead of pulling it directly from the application?

Sometimes I write small services in Go from scratch. And every time main.go ends up looking almost the same.

How to access macOS Location Services and get the geographic location of the device from Go (with the help of some Objective-C).