LWN: Comments on "Go 1.25 released"

about time

hmh — Tue, 19 Aug 2025 11:29:14 +0000

One less external dependency is always a good thing.

However, AFAIK golang's schedule is still quite *not* a thing to be praised and admired the moment you actually need high-throughput AND syscalls. I am pretty sure we will need to force GOMAXPROCS around at work in the k8s clusters (where we typically need at least a 2:1 go-max-procs to container-cpu-cores ratio for a decent tradeoff of latency x throughput). YMMV and all that.

The GC and std lib improvements being done lately were much appreciated, though. They help a *lot*.

about time

Comet — Mon, 18 Aug 2025 19:40:58 +0000

It's not like this was unachievable before, it's simply changing the defaults to respect it.

It has been, AFAIK, fairly common to import `go.uber.org/automaxprocs`; that doesn't need an explicit library call, an underscore import is fine, an init function will do the registration.

So it's good to see this now be the default (0 lines of code better than 1 line of code, and saves folks from a learning experience), but it's far more "housekeeping" than "change in capabilities".

about time

jtaylor — Thu, 14 Aug 2025 11:27:54 +0000

Finally container awareness! golang is so heavily used in container landscape (i.e. kubernetes) and every single golang using deployment needed to be adjusted to respect cpu bandwidth or suffer from quite significant performance loss and memory usage increase
That this took so long is astonishing, even java added this years ago (~v17 I think)