Finding headroom in existing hardware, and locks that fail

More headroom from the same hardware

Some of the week's best engineering came from using existing resources more carefully. Cloudflare's engineering blog describes cutting another 100TB of RAM by applying math to how memory is used. At that scale, small savings in data structures on each node add up across the fleet. PrismML is making a similar argument for models. The company says Bonsai 2 27B achieves near-lossless compression in a footprint nine times smaller, which matters most to teams whose model serving is limited by memory.

Daniel Lemire's look at how AMD Ryzen chips got roughly 50% faster in two years carries a warning for anyone who reasons from benchmarks. With gains that large, measurements taken on older hardware may mislead, and not every microarchitectural improvement shows up in real code. Before treating a profile as current, check which machine produced it.

Demand is still rising. Wired reports that AI agents are pushing up requirements for compute and power, which raises questions about energy use and infrastructure as these systems scale. Hardware supply may broaden as well: Nikkei Asia reports that Fujitsu plans to export AI chips built on its supercomputer technology to the U.S. and Asia. Work like Cloudflare's does not remove that pressure, but it shows how much capacity can sit unused in software that already runs.

What platform owners choose to publish

GrapheneOS points out that Android 17 is the first release since 3.x to add new APIs without releasing them to AOSP. For alternative ROMs, and for anyone who follows platform changes through the open source tree, that means new interfaces ship with no public code to read or build against. Projects that depend on AOSP may need to wait, or work without source.

Rheinmetall moved the other way and has open-sourced the protocol behind its Battlesuite connected weapon system, with versioned onboard API documentation now public. Outside developers may find integration easier as a result. Apple, meanwhile, published release notes for the Xcode 27.1 beta. iOS and macOS teams should check them for compiler, SDK and known-issue changes before moving CI to the beta.

Protections that depend on untested assumptions

Ledger's Donjon team used photon-emission analysis to guide laser fault injection and enable secure debug on the Raspberry Pi RP2350. In practice, an attacker with physical access can get past the debug lock on a widely used microcontroller. Products that keep secrets on commodity parts like this one need protections that do not rely on that lock alone.

Chrono Trigger offers a lighter version of the same problem: players can defeat the Dream Devourer boss by exploiting an integer overflow. Fixed-width arithmetic that nobody checked made it into a shipped game. In both cases a limit the designers treated as fixed turned out to be something an outsider could push past.

Weekend reading on ranking and complexity

A 2013 deep dive into how Hacker News ranking really works is worth reading again. It reverse-engineers the gravity-based scoring formula, the controversy detection and the penalties that demote stories, and it remains a concrete reference for anyone designing feed ranking or anti-gaming heuristics. NDepend's explainer on cyclomatic complexity in C# covers how the metric measures branching in code and why keeping it in check helps maintainability.

For something away from the screen, the New York Times visits the shop that fabricates New York City's more than one million street signs. It is a short look at manufacturing and maintenance logistics at city scale.