Bun 1.4 shipped this week with Bun.WebView, a stable API for driving the operating system's own webview from inside a Bun process. Simon Willison built a working JSON API on it the same day: post a URL, get back rendered HTML, extracted text, or a screenshot, with no Playwright, no Puppeteer and no bundled browser. The number that matters is roughly 400MB, which is what a container carries today so that a link enricher can read an OG tag. For any tooling that needs to see a page the way a browser renders it, screenshot generation, OG-tag extraction, scraping sites that assemble themselves in JavaScript, that weight has been the price of admission. The caveat is real. Rendering happens in the system's native WebKit on macOS; on Linux and Windows, Bun.WebView drives an already-installed Chrome, Chromium, or Edge over the Chrome DevTools Protocol rather than bundling anything, so output can differ by platform and by whatever browser happens to be on the host, and headless server support isn't documented.
The other thing that got lighter this week was a verdict. Anyone who benchmarked Ornith 1.5's 35B-A3B variant on launch day and filed it under disappointing was measuring the inference stack. An r/LocalLLaMA teardown traces the throughput to how the model's multi-token prediction head interacts with current runtimes, and the same checkpoint with MTP disabled produces a different number. Thursday's edition covered how fast the tooling under a model name moves now. This is that clock applied to benchmarks: a day-one throughput figure has a shelf life of about a week, and the runtime patches tend to land before the reviews do.
A week after launch, the Qwen3.8 posts have changed character. They are about what people are making out of it. Someone noticed that 3.8 and 3.6 share an architecture and had 3.8 merge the two into a single checkpoint at zero training cost. Merging stays one of the cheaper levers available when two checkpoints have different strengths on the same eval set. Tuesday's edition looked at the distance between the scores Qwen3.8 posted and the quantized weights most people can actually run. The follow-on is that the argument over whether it is the local default appears to be finished, settled by people building on top of it rather than by anyone winning it.
On hardware, the weight came off a different way: a builder ran DeepSeek V4 Flash at 130 to 150 tokens per second on sixteen 5060 Tis behind a pair of PCIe switches, and called the result boring. The switch topology is the part that carries: host PCIe lane starvation is the usual wall on cheap multi-GPU rigs, and this documents a way around it. V4 Flash has turned up three times in six days as the model people benchmark their rigs against, which makes those posts a consistent reference point when self-hosted inference gets priced against an API bill.
Furthest from AI, and possibly the most immediately useful item of the week, is another line item getting lighter: Zoneless, an open-source alternative to Stripe Connect, built by a founder who was paying around $9,000 a month in Connect fees on their own marketplace, with wider seller-country coverage as the second motivation. Payout fees decide whether low-margin marketplaces exist at all, and that line item has had very little competitive pressure on it for years.
Of everything this week, the one to carry is the take-home coding test writeup on codedge: a plausible interview repository that compromises the machine of whoever clones it, runs npm install and hits play. The attack itself is old. Its reach is what changed, because that exact sequence, clone a repository, install it, run it to answer a question, now happens dozens of times a day on ordinary machines with nobody reading anything first, since an agent is doing it. I keep landing on the asymmetry: the interview candidate at least skims the README.