Old and new apps, via modern coding agents

What xAI's Grok build CLI sends to xAI: A wire-level analysis

Mesh LLM: distributed AI computing on iroh

Hello HN!I&#x27;m the author of Ant, a JavaScript ecosystem built around a runtime with its own JavaScript engine. Ant also includes a package manager, the ants.land package registry, a platform for deploying and hosting applications, and Ant Desktop for building native desktop apps with web technologies, similar to Electron.The goal is for these pieces to work as one coherent platform while remaining compatible with the wider JavaScript ecosystem. It&#x27;s still early, and I&#x27;d appreciate any feedback on the overall direction or what you&#x27;d like to see from an e2e alternative to the existing JavaScript stacks.P.S. I’ve shared Ant here before as a runtime; since then, it has grown into the broader ecosystem you see today.

Show HN: Ant – A JavaScript runtime and ecosystem

How Doctors die. It’s not like the rest of us (2016)

Ghostel.el: Terminal emulator powered by libghostty

RISCBoy is an open-source portable games console, designed from scratch

Stop Telling Me to Ask an LLM

Under federal rule, colleges must leave grads better off or lose financial aid

How to Read More Books

This started based off of a hunch. We usually use OpenCode, but were &#x27;forced&#x27; to use Claude Code for a while due to issues with Meridian. In that time, we saw the usage meter rise much, much more quickly than when using OpenCode.This was the initial anecdotal evidence, but we undertook this small study to collect empirical data:We added logging between the agentic coding tool (Claude Code and OpenCode) and Anthropic&#x27;s endpoint, and captured all requests (and the returned usage blocks).With one caveat (toward the end of the post) we found unambiguously that Claude Code was far more inefficient in terms of its cache strategy and its harness token usage than OpenCode.