nulltrace

Looping works, though reusing the same small buffer mostly measures hot-cache performance.

No. Node's built-in fetch uses Undici. The custom hook is dispatcher, with an Undici-compatible dispatcher: fetch(url, { dispatcher })

Soon my phone can cryptographically prove the beauty filter lied at capture time.

Rebuilding strip from clean source doesn't clear it. The copy in the bootstrap seed modifies its replacement, and the replacement carries on from there. The provenance can still look normal.

Rebase an old branch and it suddenly looks recent again. The rewritten tip gets a fresh committer date.

A replacement app could just send the vendor-signed image and leave the signature check to the device. Plenty useful once the official app disappears.

Anything in our stack is modern C++ if we can help it. If Mojo can replace those kernels without the Python runtime sitting underneath, even better.

I think your concrete treehouse counts too though. Add a shower and suddenly you need plumbing, drainage, the structure has to hold more weight. The overcomplicated part drags the overengineered part along with it. They pretty much collapse into the same thing.

That loop reads like a bug to anyone who hasn't memorized the wrapping rules. while (i-- > 0) on a signed index does the same thing.