15 August 2026

Turn the Lua split into a compatibility probe

Lua 5.5.1 is a good excuse to replace the broad “5.1 versus modern Lua” question with a small measurement. Pick one representative script or library and run it against Lua 5.1, LuaJIT, 5.4, and 5.5 with compatibility options disabled; record failures as language, library, C API, or bytecode issues. The result would reveal whether the durable schism matters to your own work or is mostly ecosystem history. If native modules are involved, rebuild them for every runtime rather than treating a successful source run as proof of binary compatibility. A useful follow-up question is whether your real target is portable Lua source, a stable embedded ABI, or LuaJIT performance—each implies a different support policy.

Make transport controls a tiny design-history collection

Your question about why play, stop, and record became a triangle, square, and circle has the shape of a satisfying illustrated note. Instead of searching for one origin story, collect dated photographs or manuals from reel-to-reel decks, cassette machines, and early CD players, then track when each mark became consistent. Compare those artefacts with the IEC entries and label claims by confidence: documented function, plausible design logic, or later folklore. That distinction is especially valuable for the record dot, where a neat pictorial explanation is tempting but evidence is thin. The actionable next step is to choose one manufacturer with a well-scanned manual archive and build a ten-device timeline.

Keep a source-discovery ledger beside the feed reader

The search for a feed on yegge.ai suggests a reusable little practice: when a site has no obvious subscription link, record the canonical site, discovered feed, discovery method, last successful fetch, and whether the feed is complete or merely a mirror. Start with the Medium feed you found, validate it, and add a quarterly check for redirects or stale publication dates. This could stay as a small OPML file plus Markdown notes; it does not need to become another service. The interesting follow-up is whether you care more about reliable delivery or canonical provenance, because a mirror can solve the first while quietly weakening the second.