My favorite from this week is the Jira Turing-completeness piece, because it's exactly the kind of useless-but-rigorous computer science I keep coming back to read. Honorable mention to the Doom-in-terminal, because running Doom is the essiential part of the programming.
News
Chrome's I/O recap covers 15 updates centered on the agentic web—WebMCP, Chrome DevTools for agents, Modern Web Guidance, and expanded built-in AI APIs. Plus HTML-in-Canvas, element-scoped view transitions, and Gemini in Chrome on Android with auto browse, Skills, and voice prompting.
Proposed web standard for exposing structured tools to AI agents via JavaScript and HTML form annotations. Idea is to let pages tell agents exactly how to interact with their features instead of agents guessing from DOM. Curious to see if any other browser picks this up.
Collection of evergreen skills for AI coding agents to help them write accessible, performant, and secure web code. Plugs into Claude Code, Copilot CLI, and Antigravity. Finally something to push back on agents that still emit `<div onclick>` in 2026.
Article
GitHub rebuilt Issues navigation around a local-first model with IndexedDB caching, stale-while-revalidate, preheating likely-next issues, an in-memory hot cache, and a service worker that intercepts hard navigations to serve a thin HTML shell. Instant React navigations went from 4% to ~70%, cache-hit ratio ~96%, P50 HPC from 1,200 ms to 700 ms. Great architecture writeup.
Evil Martians on why most apps quietly break for Arabic, Hebrew, Persian, and Urdu users. Two fixes carry most of the weight—`dir="auto"` on free-form inputs so direction follows typed content, and `dir="rtl"` on `<html>` plus CSS logical properties (`margin-inline-start` and friends) for fully localized apps.
Live demo of the new HTML-in-Canvas proposal—real DOM nodes textured onto a 3D Stanford dragon, fully interactive. Cursed in the best way, and a useful concrete look at what the upcoming API actually enables.
Platformatic wires Node.js FFI to the native doomgeneric engine, with OpenTUI for rendering and SDL2 for audio, to run Doom in a terminal. Real point beneath the meme: FFI lets teams keep working native libraries and wrap them in Node instead of rewriting or shoving them behind a sidecar service.
Library&tools
Audits npm packages before install by running "marshalls" for known vulnerabilities, suspicious install scripts, typosquatting, expired maintainer domains, and package age/popularity; then hands off to npm, yarn, or pnpm. After this year's supply-chain mess, drop-in wrappers like this start looking less paranoid and more required.
Feeds your real GA visitor data into Baseline targets so you can pick the cutoff that actually matches your audience instead of guessing from caniuse. Small tool, very practical.
Side-by-side comparison of component syntax across React, Vue, Svelte, Solid, Angular, and friends. Handy when you're context-switching between stacks or trying to explain to a Vue dev what `useEffect` actually does.
React bindings for declarative GLSL shaders—compose effects like components, with props feeding uniforms. The hellogl example is a 5-line intro that ends with you rabbit-holing into fragment shaders for the rest of the afternoon.
Other
Nicolas Seriot encodes a Minsky register machine in Jira—Epic status as program counter, linked Bugs/Tasks/Stories as registers—then implements addition and a three-state Fibonacci machine. Concludes Jira automation can encode a two-counter machine given unbounded issue creation. The funniest "it runs Doom" energy of the week without actually running Doom.