A new Git version just dropped and it comes with a new experimental `history` command!
`reword` can be used to change commit messages and `split` can untangle a single commit into multiple ones.
No more interactive rebase. 🎉
github.blog/open-source/...
My guess was Brad's enthusiasm for talking about Unicode encoding & modifiers while at the dermatologist had circulated within the PNW dermatologist community...
But no 😅
Go’s push iterators can be strange at first but they are so much easier to write when the algorithm to visit the elements has nontrivial control flow (recursion or conditionals) such as for a tree; you just call yield. In Java/C++ one must explicitly materialize all state implied by your SP and PC.
Building Go APIs with Huma, sqlc, and Goose
blainsmith.com/articles/bui...
#GoLang #SQL ##OpenAPI #huma #sqlc #goose #codegen
Holy cheese my untyped composite literal proposal from 2015 just got accepted. #golang github.com/golang/go/is...
A Fast Immutable Map in Go lemire.me/blog/2026/03/29/a-fast-i...
Have you seen exe.dev yet?
It seems well done.
The VMs are locked down to you by default, but with some convenient sharing options. (Started by one of the co-founders of Tailscale).
exe.dev/docs/sharing
Could Go be a better C? I think so!
Meet Solod — a strict subset of Go that translates to C, without hidden memory allocations and with source-level interop.
antonz.org/solod
This is the best product review I’ve read: samhenri.gold/blog/2026031...
It doesn’t matter if you’re interested in the MacBook Neo or not; this is the kind of essay that makes you think about the potential of technology and the joys of exploration.
A great example of how the Google #golang team put thousands of lines of ultra-technical code in service of an incredibly easy-to-use and useful tool. If you ever deprecate code, you really should know about the go:inline directive!
Find out how the source-level inliner in Go 1.26 can help you with API migrations.
go.dev/blog/inliner
I've spent the past couple months hand crafting a new B-tree map implementation for Go. It's fast. Faster than Rust's BTreeMap. Faster than the fastest C++ (frozenca/btree). And about 2x faster than my current Go btree (tidwall/btree).
I've just released a new version of the "sh" #golang module, including initial Zsh support in shfmt, as well as many improvements and fixes to the parser and interpreter 🎉
Finally! No more "dirty" #golang builds because you have untracked files laying around which don't affect the build at all :)
Got an idea buzzing in that brilliant gopher brain of yours? 🧠
Don’t keep it in the lab; share it with the #golang community! 🧪
#GopherCon Call for Speakers closes March 4th.
Submit your proposal ➡️ sessionize.com/gophercon-20...
#RoadToGopherCon
(Many of the problems flagged by gopls also come from go vet, and the core Go team maintains an additional set of excellent code analyzers that are also used by gopls, but Dominik's Staticcheck is much broader than either of those.)
Small #golang PSA:
Most of the very nice automatic code problem reports in your editor or IDE come from Staticcheck by Dominik Honnef (@honnef.co).
gopls is the LSP, and it uses many of the rules from Staticcheck.
Suggestion: consider sponsoring Dominik! (Well worth it in my humble opinion😅)
I'm putting the finishing touches on the Staticcheck update for #golang 1.26. You can expect a release by the end of the week.
Some pretty awesome improvements in 1.26 for compiling/testing typescript-go.
With a clean build/test cache, running the full test suite used to take 3m45s, but now takes just 2m10s.
Go 1.26 is out, and the announcement says:
"Over the next few weeks, follow-up blog posts will cover some of the topics in more detail. Check back later."
So you can wait a few weeks OR you can read my interactive Go 1.26 tour right away:
antonz.org/go-1-26
With Go 1.26, you can easily log to multiple targets (like stdout, a file, or a remote server) using just the standard library.
All thanks to slog.MultiHandler, which sends log records to any number of handlers you configure.
I think some @tangled.org folks are at FOSDEM if you want to talk to them about stacked reviews use case and comparison with Gerrit.
Maybe you could help ever-so-slightly nudge the industry forward on the goodness of Gerrit. 🤞
(And maybe in parallel you can nerd snipe them into using some CUE 😅)
@rog.bsky.social this sounds perfect for testing servers locally, especially with synctest 😊
github.com/golang/go/is...
This is a fun writeup of using C to implement #golang interfaces (or maybe Rust traits), complete with editable C you can run via your browser.
It pairs nicely with the classic post on the Go interface implementation by @swtch.com from 16 (!) years ago:
research.swtch.com/interfaces
“Floating-Point Printing and Parsing Can Be Simple And Fast”
The fastest known floating-point printer and parsing algorithms - fixed-width printing, shortest-width printing, and parsing, all in 400 lines of Go.
research.swtch.com/fp
research.swtch.com/fp-proof
Maybe you were thinking of this from earlier this week?
bsky.app/profile/apen...
And to be clear, that's not some backhanded complaint. 😅
I'm glad folks in academia study FOSS ecosystems, which seems like a treasure trove of interesting research questions, and they cleanly cited everything.
The two main issues I think were:
go.dev/issue/31543
go.dev/issue/32695
There's also this 2021 paper:
arxiv.org/abs/2102.12105
It's more specific to some Go modules transition pains
(For me, reading that paper felt odd because I kept saying "huh, I recognize that example" and then slowly realized large portion of the paper was based on ~3 GitHub issues I had filed 😅)
@michael.express and @prattmic.com, you'll likely be pleased to see this 🚀
