proposal: go/ast: standardize deprecated comment tags
Read on GitHub Proposal Details Background Different Go tools already supports detecting "Deprecated:" strings in the doc comments for symbols (see https://go.dev/wi
Issue #33
Range-over-channel goroutine leak revives the structured concurrency wish
The discussion to read is a developer owning up to the classic range-over-channel goroutine leak while building a cron scheduler, and using it as a case for structured concurrency in Go. It is a well-trodden bug (Uber's concurrency guide flags it) but the post is a clean retelling of why the language still leaves this trap open. On the proposal track, there is a pitch to standardize "Deprecated:" comment tags in go/ast, pulling an existing tooling convention into something the compiler toolchain agrees on. Elsewhere, a write-up on socket-activating a Go HTTP service via systemd is a nice reminder that the boring Linux primitives still pair well with a single static binary.
Wednesday, June 24, 2026 · Issue #33
🐿️ Range-over-channel goroutine leak revives the structured concurrency wish
The discussion to read is a developer owning up to the classic range-over-channel goroutine leak while building a cron scheduler, and using it as a case for structured concurrency in Go. It is a well-trodden bug (Uber's concurrency guide flags it) but the post is a clean retelling of why the language still leaves this trap open.
On the proposal track, there is a pitch to standardize "Deprecated:" comment tags in go/ast, pulling an existing tooling convention into something the compiler toolchain agrees on.
Elsewhere, a write-up on socket-activating a Go HTTP service via systemd is a nice reminder that the boring Linux primitives still pair well with a single static binary.
Proposals 1
Discussions 7
I just wrote the classic "range over channel" goroutine leak. Structured concurrency in Go would be nice.
Read on Reddit Wrote the range-over-channel goroutine leak while building a small custom cron scheduler. The leak is well-documented, and Uber included it as one of the most common concurrency bugs. I have debugged
Today's # Devops / # Cloudops challenge: My engineers are asking why # AI token
Read on Mastodon Today's Devops / Cloudops challenge: My engineers are asking why AI token caps are so low....my answer..... "Learn to write some python / golang / etc and stop being so dependent, goofballs."
The beauty of tech blogging: Others describe the traps they fell into so you can
Read on Mastodon The beauty of tech blogging: Others describe the traps they fell into so you can learn from their experience. https:// newsletter.appliedgo.net/archi ve/2026-06-21-the-smart-gopher-gets-the-cheese/ go
Database Engine Creation using Go.
Read on Golang Nuts "I want to build a low-level project for my resume. An LLM suggested creating a database engine in Go, but I’m unsure how to approach it. Should I pursue this project, or focus on something else? If
Build UtubeWatchTogether using Go
Read on Golang Nuts Over the past few weeks, I've been working on a real-time watch party application built with Go. UtubeWatchTogether allows users to create rooms, synchronize video playback, chat in real time, and com
Open source client for deps.dev API
Read on Reddit Free access to dependencies, licenses, advisories and other critical health and security signals for open source package versions. GitHub repo: https://github.com/edoardottt/depsdev https://deps.dev/
Socket-Activation for a Go HTTP service on Linux with systemd
Read on Reddit systemd on Linux can run your Go webapp only when it actually receives requests. With this, your Go executable will start with the first request it receives - and that first request will succeed. A li
Articles 5
Understanding Error Handling in Go: Errors as Values, Exceptions, and Type-Safe Alternatives
Read on Medium The Three Ways Languages Handle Failure Continue reading on Medium »
You should own your AI memory, the KISS Golang way — Part 1: ChatGPT
Read on Medium In which we extract a few years of our own thinking from a server we do not own, and put it back where it belongs: on a disk we can hold… Continue reading on Medium »
State, Threads, and Processors: A Low-Level Analysis of Go Concurrency
Read on Medium If you’ve ever written go function() in Go, you've used a goroutine. They're lightweight, cheap, and powerful. But what actually happens… Continue reading on Medium »
Rust Reduced p99 Latency by 41%. Go Reduced On-Call Incidents by 58%.
Read on Medium The decision between Go and Rust. The queue depth graph looked wrong. Continue reading on Medium »
We Added Circuit Breakers to Every Service. Then We Turned Half of Them Off.
Read on Medium Continue reading on Medium »
Videos 5
Stop Overpaying for K8s Dev Previews
Read on YouTube Stop using Kubernetes for simple dev previews. Learn why a Go + Docker binary is the faster, cheaper alternative for ephemeral ...
Golang Microservices Full Course #11 - Unit Testing
Read on YouTube Build a Wallet App with Go – EP11: Unit Testing in Go In Episode 11, we dive into Unit Testing and learn how to write reliable ...
Go Fiber Middleware Explained: Build Faster APIs with Golang Fiber (Step-by-Step)
Read on YouTube Middleware is one of the most important concepts in backend development. In this episode, you'll learn how middleware works in ...
Solving "Everybody Codes" 2025 challenge, quest 20
Read on YouTube I continue my series of videos on the 2025 "Everybody codes" challenge with quest 20, solved as usual in golang. Sorry about the ...
Trending 2
kunchenguid/treehouse
Read on GitHub Trending Manage worktrees without managing worktrees.
Social 1
"Talking Heads From The Year 2053 - Episode One" is out
Read on Bluesky "Talking Heads From The Year 2053 - Episode One" is out! At last, Episode One of the show that answers your most important questions about the future, from the future. Go watch it right now! youtu.be/