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

PyTorch BlogTools

Building Spyre as a Native PyTorch Device

October 8

TL;DR Spyre becomes a native PyTorch device by connecting PyTorch’s existing device, allocator, stream, and compiler abstractions through torch-spyre to the Spyre runtime and firmware.

Languages & runtimes

Read at PyTorch Blog ↗

One letter a week, in your inbox.

Latest

Building Spyre as a Native PyTorch Device

Related

SiliconSolo developer rebuilds Adobe Creative Suite in Rust using Claude, releases it free to all Tom's Hardware

SiliconGoogle Working To Leverage More Compiler Optimizations Within The Linux Kernel Phoronix

AsiaSwish tests no-fee restaurant delivery with Swish Go: We compared its prices with Swiggy and Zomato MediaNama

JapanRust版TypeScriptコンパイラとClaude Haiku 5.5の最新トレンド解説 Zenn (AI)

Languages[$] LWN.net Weekly Edition for October 8, 2026 LWN

Toolsrust-v0.162.0-alpha.19 Codex releases