Targeting Go 1.28 — Updated for status (adonovan): - [x] Scanner.Err analyzer implementation, enabled in gopls (https://go.dev/cl/730480) - [x] sql.Rows analyzer implemen
Go 1.28 to flag missing Err checks on bufio.Scanner and sql.Rows
An accepted proposal adds vet analyzers for the two Err-check bugs everyone has written at least once, catching missing bufio.Scanner.Err and sql.Rows.Err calls in Go 1.28, with the gopls implementations already landed. On the discussion side, r/golang is asking whether chi still earns its keep now that the standard mux has grown up, which is a fair question to sit with while the toolchain quietly closes off another class of silent failures.

An accepted proposal adds vet analyzers for the two Err-check bugs everyone has written at least once, catching missing bufio.Scanner.Err and sql.Rows.Err calls in Go 1.28, with the gopls implementations already landed. On the discussion side, r/golang is asking whether chi still earns its keep now that the standard mux has grown up, which is a fair question to sit with while the toolchain quietly closes off another class of silent failures.
I often see people criticizing CGO (and for good reasons), mainly because it bypasses many of the safety guarantees and tooling that Go provides. There are also issues involving the interaction betwee
Mobile backends, customizable widgets, and progressive tutorials
Hi all, I wrote up something on a performance footgun most of us walk right past. io.Copy looks innocent, but it is doing a lot more copying than you would think. https://medium.com/dev-genius/zero-co
Hi everyone! We've been working for a while on a new version control and software forge written in go, and recently decided to open source it! I've learned a lot since i started and the code saddly st
form v1.9 — worth the upgrade from v1.5.x / v1.7.x If your project pins an older — v1.5.1 and the v1.7.x line are the versions most often seen in the wild, usually pulled in indirectly — v1.9 is
Hello everyone, i am looking for quantum traders, go lang developers, c++ devs for my quantum trading group. with aim to become and firm in the future we are looking for determined people to join us.
Join Golang Reston @ Online on Wed Aug 19
While building GILLZY, a digital goods marketplace, I ended up working on a problem that appears in...
In which the author admits to writing Rust, disappoints the critics and the cultists in a single sitting, and defends his choice with… Continue reading on Medium »
Facebook and Google detect billions of duplicate images instantly — here is the clever algorithm behind it. Continue reading on Medium »
Three weeks of intermittent failures, an hour spent blaming the wrong team, and a promise the client never actually made. Continue reading on Medium »
Go crushes Python in speed — so why do AI developers refuse to switch? The answer will surprise you. Continue reading on Medium »
A short capture showing how to prepare the codebase of this library to start working on it using AI agents (Cursor IDE).
We already prepared the codebase to work on it with AI Agents (Cursor IDE). Time to do the first task: upgrade a dependency.
Using AI agent (Cursor IDE) to document how code works. So later when we develop further functionality we can simply refer to ...
Details: In this video i explain the singleton design pattern with an easy example tahidur rhaman munna bangla.
Open-source & free — Battle-tested at Alibaba's scale. Hybrid architecture code review tool: deterministic pipelines + LLM Agent, precise line-level comments, built-in fine-tuned ruleset (NPE, threa
Secure sharing of secrets, passwords and files

Added LAN Orangutan to the list of Go libraries.
Gitea: Unbounded Arch package file metadata can cause resource amplification in Gitea package uploads in gitea.dev
Gitea: Personal access token scope enforcement bypass on the repository home page ( ) discloses private repository contents in gitea.dev
Gitea Docker image: default lets any source IP impersonate any user via in code.gitea.io/gitea