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

LWNLanguages

[$] Owning C types from Rust code

October 13

Rust's system of ownership and borrowed references is convenient when it can correctly model a program's needs.

Languages & runtimes

Read at LWN ↗

One letter a week, starting soon.

Latest

[$] Owning C types from Rust code

Related

SiliconAll Systems Go: Global PC App Ecosystem Ready for NVIDIA RTX Spark NVIDIA Blog

ValleyWikipedians Believed AI Would Come and Go. They Were Wrong Wired AI

ToolsPython vs Go: A Practical Comparison for Developers JetBrains Blog

GitHubShow HN: SolidCraft – Open-Source Parametric CAD in Rust (With MCP Support) Hacker News Show

LanguagesPython 3.16.0 alpha 1 is now available Python Insider

LanguagesRyan Dahl: 'Why reimplement Node? It works.' JavaScript Weekly