Very nice! #golang flight recorder taking off (so to speak)

A good way to keep up with the Go project is this starter pack from @mvdan.cc (long-time #golang contributor). Two other good ways to keep up are subscribing to the Go proposal review meeting GitHub issue: go.dev/issue/33502 and the Go compiler & runtime meeting notes issue: go.dev/issue/43930

New blog post, with a perhaps mildly unpopular opinion: jayconrod.com/posts/133/in...

Related #golang PSA: Gophers often mistakenly put a -u in 'go get -u foo', when they would have been better off with just 'go get foo'. 'go get foo' says to upgrade foo itself. It's shorthand for 'go get foo@upgrade' 'go get -u foo' says to *also* upgrade all the direct and indirect deps of foo.

30 Years of Programming at 44 Years Old blainsmith.com/articles/30-... #Programming #Birthday

Tailscale, AT protocol, #golang, holding hands running through a field

Go did this best in my opinion. The "time" package's API is a work of art: want the current time? ```go time.Now() ``` want time since an operation? ```go t := time.Now() elapsed := t.Sub(start) ``` Need a ticker every 5 seconds? ```go timer := time.NewTimer(5 * time.Second) <-timer.C ```

New #golang Reed-Solomon release. Contains new progressive field decoding and some significant speedups. Check it out: github.com/klauspost/re...

Seeing an influx of people starting out their adventures building in the atmosphere or asking how to, so here’s my statusphere demo app built in #golang as reference. tangled.org/willdot.net/...

So the second most imported 3rd-party dependency is Google's own UUID package. I wonder what it would take to convince the Go team to add it to stdlib. Also, I don't think x/crypto and x/net should be here at all. Both are imported by stdlib itself, so they're basically included in every project.

“Pulling a New Proof from Knuth's Fixed-Point Printer” Happy 88th Birthday to Don Knuth! And thanks again to @robpike.io for Ivy. research.swtch.com/fp-knuth

Go 1.26 will be huge for the ecosystem thanks to massive improvements in the garbage collector: > Benchmark results vary, but we expect somewhere between a 10—40% reduction in garbage collection overhead in real-world programs that heavily use the garbage collector. Exciting!! go.dev/doc/go1.26

Coming in at number 5 with over 93,000+ dependents, cobra is more than just a Go library: it's a core par of the breathing ecosystem. It's been a pleasure shepherding this library for the better part of 5 years. To the whole Go community, thank you!!! blog.thibaut-rousseau.com/blog/the-mos...

I don't have a large collection, but it is timeless. #Books

Feels like writing assembly minus the part where you typo on letter and create an Remote-Code-Execution vulnerability. Really exciting stuff to play with !

Hi @mcy.gay, looking over Go SIMD proposal, I'm reminded you expressed some interest in giving it a quick whirl once it was merged. I'm curious if you've had a chance to try a hello world or port some code or whatever? (and fyi, there's been some tweaks since go1.26rc1, so tip is probably better)

Right now, and the next few months, is a very good time to talk about that organization, since an "experiment" is technically still up for change. The argument *for* archsimd is that long term, it will all be build-tag gated, a smaller number of Go programmers will be using low level simd

Go 1.26 brings the long-awaited vectorized operations (SIMD) in the simd/archsimd package. Since it's hard to create a portable high-level API, the Go team decided to start with a low-level, architecture-specific one and support only amd64 for now.

I have written self-tests for the Python test generator and added tests to the Go tests. Folks, I can confirm we got all the edge cases! 💥 🥳 Thank you so much to everyone who contributed to the > 8,500(!) cores. I would like to credit you, so either reply or DM me your name/handle, if you'd like.

Go 1.26 received a somewhat under-the-radar language change: recursive type constraints in generics. Previously, type constraints couldn't directly or indirectly refer to type parameters. ↓

My GopherCon talk was just posted!

Hi @antonz.org, good question! Something like 'make([]byte, 0, 33)' does indeed create a slice with a capacity of exactly 33, as your example shows. However, the underlying allocated heap object actually is larger. Quick playground example that hacks things to print the heap object size:

Hey @thepudds.bsky.social! Thanks for io.ReadAll in Go 1.26 :) Why did you choose to use append-make instead of just make for the final slice? Using append-make sets the slice capacity to the next size class, which seems to go against the idea of having a "perfectly-sized slice", doesn't it?

This is an excellent interactive overview of upcoming #golang 1.26 changes put together by @antonz.org 🚀 (And @antonz.org -- I appreciate the shoutout there about you enjoying reading my CLs! Now that I know at least one other person might read them, I'll try not to let you down in the future 😅)

Go 1.26 is coming soon, and the official release notes are pretty dry. So I prepared an interactive version with lots of examples. Read on and see! antonz.org/go-1-26

Profiling Request Latency with Critical Path Analysis, @felixge.de @ GopherCon 2025 www.youtube.com/watch?v=BayZ...

My GopherCon lightning talk on the Lua interpreter I built for zb is now up! #golang youtu.be/BVLgLZ6_ZHo

What's new in gopls 21: go.dev/gopls/releas... Please try it out: $ go install golang.org/x/tools/gopls@latest

This was a fun conversation. Thanks to ACM Bytecast for having me on. learning.acm.org/bytecast/ep7...

“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...