Applied Go

Fighting cross-site request forgery (CSRF) becomes easier in Go 1.25, thanks to the new cross origin protection feature.

Why should you let tracing pile up huge amounts of data when you need only a few seconds of trace output? Meet FlightRecorder.

Before Go 1.25, GOMAXPROCS defaults to the number of available physical CPU cores at app startup time. Now it takes container limits into account and checks changes periodically.

The sync/atomic package recommends using atomic types and their methods instead of the package-level atomic functions. For good reasons.

The Go team decided to put an end to error handling syntax proposals. Time for a refresher on the kind of error handling that works well since 2009.

Tests that rely on time.Sleep() to test timings can be unreliable and slow. The synctest package introduces two antidotes: fake time and

WaitGroups are a means of synchronizing goroutines; yet the Add()/defer Done() idiom feels clumsy and is error-prone. A new method, Go(), puts an end to goroutine counting.

Programs in the Go Playground can print text to a space below the code editor. With a simple trick, you can even output PNG images.

Compiling Go code into a WebAssembly module is easy as pie. Getting the code to interact with the browser requires a few lines of Javascript, but it's less complicated than you might think.

The Go team develops a new garbage collector algorithm suitable for multicore CPU architectures and non-uniform memory. You can try it now!