The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo

← Accept All Archive

Golang WeeklyLanguages

Why Go had to hardcode a block on broken certs

10.23

#621 — October 23, 2026 Read the Web Version Go Weekly Interactive Refactoring in gopls — LSP refactorings can't 'ask' you anything, so "Add struct tags" in gopls just guessed json and camelCase.

Languages & runtimes

Read at Golang Weekly ↗

One letter a week, starting soon.

Latest

Why Go had to hardcode a block on broken certs

Related

LanguagesHooking into the Go toolchain Golang Weekly

LanguagesGo 1.27's portable SIMD Golang Weekly

SiliconHow to Read Data into GPU Memory in Python with NVIDIA GPUDirect Storage NVIDIA Technical Blog

ToolsLangSmith LLM Gateway: Runtime Controls for Agents LangChain

LanguagesRuby 4.0.8 Released Ruby

LanguagesBun v1.4.4 Bun Blog