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

Google Developers BlogLabs

Integrating TorchTPU into TorchTitan and Optimizing Models for TPU

11.04

TorchTPU integrates a native torch.device("tpu") backend directly into PyTorch, allowing developers to train large-scale models on Google Cloud TPUs without rewriting code in JAX.

Chips & compute

Read at Google Developers Blog ↗

One letter a week, starting soon.

Latest

Integrating TorchTPU into TorchTitan and Optimizing Models for TPU

Related

LabsSmaller apps and faster GPU inference with LiteRT in Google Play services Google Developers Blog

LabsAnnouncing New vLLM and SGLang Inference Engines on TPU Google Developers Blog

JapanJapan's Aisin develops new type of AI chip that cuts energy use 98% Nikkei Asia Technology

SiliconIs There Room for Small-Scale OSATs in India’s Chip Packaging Boom? EE Times

Toolsb12081 llama.cpp releases

Toolsb12080 llama.cpp releases