Weak pointers and better finalization in Go 1.24.

Someone on the Go team decided to take a "quick stab" at fixing a small bug in Go's escape analysis, resulting in a 5x increase in typescript performance.

Why Go you ask?

A novel technique for implementing dynamic language interpreters in Go, applied to the Vitess SQL evaluation engine

Better benchmark looping in Go 1.24.

Overview Change the Go runtime on Linux to use CPU cgroup quota limits to set the default value of GOMAXPROCS. This is a concrete proposal for the ideas discussed in #33803. I've included a lot...

Understand how Go’s sync.Pool affects memory usage in high-throughput systems. Learn when pooling helps, when it hurts, and how to use it safely for performance optimization.

Assert your Go code is inlined and bounds-check eliminated - jordanlewis/gcassert

The standard Go toolchain comes with an assembler out of the box. Said assembler is highly idiosyncratic, using syntax inherited from Plan 9 and choosing its own names for platform-specific instructions and registers. But it's great to have it readily available.…

Go 1.24's Swiss Tables cut our map memory usage by up to 70% in high-traffic workloads. Here's how we profiled the savings and improved performance.

New GOMAXPROCS defaults in Go 1.25 improve behavior in containers.

Update (08/20/2025): A preliminary implementation of AMD64 low-level SIMD package is being developed on the dev.simd branch. You're welcome to check it out and try it with your use cases. Feedb...