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

The New StackGitHub

Google and AWS open new paths for PyTorch beyond Nvidia

10.22

At PyTorch Conference North America 2026 this week, Google open-sourced TorchTPU , a native PyTorch stack for Google TPUs, now available on GitHub .

Chips & compute

Read at The New Stack ↗

One letter a week, starting soon.

Latest

Google and AWS open new paths for PyTorch beyond Nvidia

Related

VoicesWhat will computer chips look like in 2045? Dwarkesh Podcast

SiliconNVIDIA Unveils Minerva to Bring End-to-End Observability for AI Factories NVIDIA Blog

Asia‘Jensen’s nightmare’: Huawei, DeepSeek narrow AI chip ecosystem gap with Nvidia: report SCMP Tech

SiliconGoogle’s TPUs for AI workloads now run in Meta's data centers Tom's Hardware AI

SiliconEverspin Expands MRAM Push into AI Servers, Data Centers, Satellite Systems EE Times

SiliconChip Scaling Moves Beyond The Transistor SemiEngineering