“Go’s Sweet 16” by Austin Clements, for the Go team — https://go.dev/blog/16years #golang

I'm proud to officially announce CUE Labs! I co-founded CUE Labs with @myitcv.io to build a Configuration Control Plane, solving config chaos with CUE. Our work also provides the stewardship for the @cuelang.org open source project. Read our launch post: cue.dev/blog/announc...

So excited to finally share what we've been building at CUE Labs! Proud to be on this mission with @mpvl.io, @myitcv.io, @rog.bsky.social, @hylomorphism.bsky.social, and @dominikdm.bsky.social.

For some added fun, also see go.dev/cl/715362, wherein I discover that VPCOMPRESSQ is horrifically slow on AMD Zen 4, but only with a memory destination. And thanks to @lemire.bsky.social for writing about this, which made this much faster to track down!

If you have an interest in understanding garbage collection better, or in how Go's new GC works under-the-hood, I highly recommend reading @michael.express's thorough guide through Go's current and Green Tea GC.

I am using it to test our Go modules against the latest versions of their dependencies (with "go get -u") on a schedule, to be notified early of compatibility issues, but without the supply chain attack risk or the Dependabot churn.

Resurrecting an old post about how I write HTTP clients in Go since I am doing this again for the 89432894023 time. blainsmith.com/articles/how... #GoLang #HTTP

I see a future in #jj-vcs: steveklabnik.com/writing/i-se...

I really do like Golang being "batteries included". It took only a few hours to write a moderately featureful TLS-terminating reverse HTTP proxy that used nothing outside the built-in libraries. The only compromise was using JSON for the configuration file. I would have preferred textproto…

This is a very cool advanced #jj-vcs workflow: flames-of-code.netlify.app/blog/my-jj-w...

Oh my god it actually worked. This might be my funniest—but totally serious—cryptography engineering contribution.

@simonwillison.net with some commentary on the new CrossOriginProtection CSRF protection in the http package for #golang 1.25... 🚀

@andreabarisani.bsky.social is the author of the new-ish proposal for bare metal support for Go, which seems to be gathering some momentum AFAICT. Andrea continues to share some fairly exciting progress... 🚀 ( #golang proposal: github.com/golang/go/is... )

Fun little Go compiler CL merged today: go.dev/cl/706655 Uninlined generic functions have a "dict" arg, since Go generics are neither erased nor monomorphized, but instead instantiated for each "GC shape" (e.g. T=*int and T=*float64 get the same code, but T=int32 and T=int64 do not).

Stupid #jj-vcs tricks andre.arko.net/2025/09/28/s...

OK, I love this. tl;dr using knowledge of your allocator, speed up linked list traversal by adding a branch that guesses where the next linked list element is and pre-populates the "next" variable to eliminate stalls if the allocations are well-behaved.

If you haven't been keeping up, Go 1.21 reduced overhead from ~10% to ~1%. 1.22 overhauled the format to improve reliability and add information. 1.25 has a built in trace flight recorder. And we have an active proposal (go.dev/issue/62627) for a trace parsing package to enable arbitrary tooling.

Go's execution tracer is a woefully underutilized tool. It contains tons of information about what is happening at any given moment that you won't get with a profile. In addition to showing flight recording capabilities, this post provides a nice example of how to use tracing to diagnose a problem.

I recently spoke at GopherCon UK 2025 about the hidden power of #Go’s `-toolexec` flag. How it can turn every `go build` into a programmable pipeline for things like error-handling enforcement and observability hooks. Here’s the recording:

My talk from #gopherconuk is up on YouTube! My take on how map is implemented in Go, and what changed from Go 1.23 to 1.24 and 1.25. youtu.be/M05t7Q6LbFs * Talk contains no AI, but does contain pictures of cats.

New blog post: Security through intentional redundancy commaok.xyz/post/securit...

Screw PXE, this means the entire Go TLS and networking stack is available under UEFI. In seconds I added DHCP and an SSH server to remotely manage my pre-boot environments. I see much potential.

This talk is like the solstice, it appears twice a year :)

I've been eager to get more context and commentary on those slides. Fortunately, @dave.cheney.net gave the talk again at GopherCon Europe 2025, and the recording is now live! www.youtube.com/watch?v=RZe8...

My GopherCon EU talk about Swiss Table maps is now available! youtu.be/aqtIM5AK9t4

Ooh, the SIMD WIP stdlib API for #golang is ready for people to poke! From Cherry from a few minutes ago: > As of today, we've landed a preliminary version with a reasonable API coverage. You're welcome to check out the dev.simd branch and try it with your use cases. github.com/golang/go/is... 🚀

Predictable memory accesses are much faster https://lemire.me/blog/2025/08/15/predictable-memory-accesses-are-much-faster/

Here are the slides for my "What's coming to Go 1.25" talk at #GopherConUK! #golang

Such an awesome feature! Catch a heap profile just before your Go process is just about to be killed by the OOM killer. (truly hooking into the kernel's OOMkiller with eBPF!)

I'm so excited to be giving a lightning talk at #Gophercon! Come see me talk way too fast about programming language nerdery. www.gophercon.com/agenda/sessi...

Go 1.25 is the best release of Go yet!

🎊 Go 1.25.0 is released! 📝 Release notes: https://go.dev/doc/go1.25 ⬇️ Download: https://go.dev/dl/#go1.25.0 #golang

Excellent blog post about hooking up Go into Java for erasure coding: kohlschuetter.github.io/blog/posts/2...

I'm happy to share that my talk proposal was accepted for GopherCon in NYC! It's on the Go compiler & escape analysis. I hope to chat with you there. Yes, you! (And if we don't know each other yet, just introduce yourself, and then we can chat! 😅) #golang #gophercon

Gopls v0.20.0 is released: go.dev/gopls/releas... $ go install golang.org/x/tools/[email protected] Docs at go.dev/gopls. Thanks to all who contributed!

Check out this new blog post outlining how profiling is becoming the fourth pillar of observability 🚀. www.datadoghq.com/blog/continu...

Whenever I find myself going in circles with Go's type parameters, I revisit @rog.bsky.social's Generics Unconstrained talk. It's a reminder that sometimes interfaces are all you need and that unconstrained type parameters might be what you're actually looking for www.youtube.com/watch?v=eU-w...

Is anybody here able to put me in touch with somebody at Apple who could help with fixing setitimer(2) on macOS or figure out another approach to CPU profiling for Go and other user space programs? github.com/golang/go/is...

🚀 What happens when you port the TypeScript compiler—150K+ lines of code & 90K+ tests—to Go? You get a 10x performance boost! 💥 Join @jakebailey.dev as he dives into why Go was the perfect fit, how they tackled the port, and what was learned along the way. 🎟️ available at www.gophercon.com 😎

Excellent #golang blog post with a bunch of interesting general Go performance nuggets along with an overview of a new (and fast) Protobuf parser in Go from the folks at Buf. 🚀

Thanks @commaok.xyz for hosting @michael.express and I to talk about a fun bug in Go’s new Green Tea GC and the tools we used to investigate. sigpod.dev/6

A few ways to build Go programs with a modified compiler/runtime/standard library: nsrip.com/posts/patchr... Overlays in particular are pretty cool IMO

Slack now runs the new Go-powered @typescriptlang.org checker in CI. Using the tool saves us over 5 minutes per run, meaning faster merges and happier developers. Huge thanks to Anders, @jakebailey.dev, and everyone else on the project for the incredible performance gains.

FWIW, I think it is highly rationale & pragmatic for the core Go team to take this step. It follows one of the core tenets of Go, which is that in the absence of consensus, the default is to not make a change. As I understand it, it is also follows the tenet of "No is temporary. Yes is forever".

For #golang error handling, I think the older 'try' proposal was actually *close* to being acceptable for a healthy majority of gophers. There were very *specific* things that caused objections for 'try', but those specific things were likely solvable, with an end result close to the proposal. 1/n

Three Trail of Bits engineers audited core Go cryptography for a month and found only one low-sev security issue... in unsupported Go+BoringCrypto! 🍾 Years of efforts on testing, limiting complexity, safe APIs, and readability have paid off! ✨ Yes I am taking a victory lap. No I am not sorry. 🏆

Very impressive and thorough look at the Go runtime internals.

There are some people I admire and aspire to emulate. And others I admire and know are beyond my ken. Ian belongs to the latter.

I remember being so excited to get a CL approval from him as a Google intern (a decade ago, wow...) that I took a picture of the notification on my watch It makes me really sad to see him go, to me he is one of the reasons Go is so successful, both as a language and as a project 😥

A hearty +1 to everything said here. Ian brings a kindness and a joy to every engineering endeavor he works on.