AI makes submitting a plausible patch cheap. Verifying it still takes human time. Recent restrictions from Sindre Sorhus and SWC expose that imbalance, but their responses and stated reasons differ. The question is not simply whether AI belongs in open source. It is who pays for verification.
OJ — nicknamed "Orange Juice" — is a single Rust binary from Lovable that runs a React app the way Vite's dev server does. To be clear up front, because this is where most of the coverage goes wrong: it is not a fork of Vite's source code, and it is not a full rewrite of Vite. It reimplements one layer — the dev-server layer — in Rust, while leaning on the same Rust foundations Vite itself already uses. That correction matters, but it isn't the real story. The real story is the debate OJ set off: a Socket.dev article and a widely-shared Evan You post arguing that AI is collapsing the cost of reimplementing open-source dependencies, and what that does to the ecosystem. If you want the background on why Rust keeps showing up under node_modules, that's a separate post — see The Rust Wave Under Your node_modules. This one is about OJ specifically, and the argument it started.
Morphicons is not an icon set. It ships zero icons. It is a ~6.6 KB gzip engine that interpolates SVG d paths, so any stroke icon can smoothly morph into any other one — hamburger into close, play into pause, sun into moon. Instead of asking you to adopt yet another pack, it sits on top of the sets we already recommend: Lucide and Heroicons outline. The idea is genuinely clever. The maturity is genuinely worrying. Both are worth a closer look.
AI coding agents waste a remarkable number of tokens just figuring out how your code connects. They open file after file, read imports, chase type definitions, and slowly build a mental model of architecture — burning through context windows and money in the process. @ttsc/graph takes a different approach: it hands the agent a compiler-resolved architecture graph upfront, so it can navigate by structure instead of reading source. It's early (v0.16), requires TypeScript v7 rc, and the benchmarks are vendor-supplied — but the idea is sharp enough to be worth knowing about. The author is Jeongho Nam (samchon), known for typia and nestia, which adds some credibility to the execution.
AG-UI (Agent User Interaction Protocol) is an open, event-based protocol that standardizes how AI agents communicate with user-facing applications. Created by CopilotKit and adopted by Microsoft, Google, AWS, LangChain, and CrewAI, it fills the gap between MCP (agent↔tools) and A2A (agent↔agent) by defining the agent↔UI layer. It's MIT licensed with 14.4k GitHub stars and 50+ framework integrations.
The Model Context Protocol specification release candidate (locked May 21, stable July 28, 2026) makes the protocol fully stateless — no handshakes, no session IDs, no sticky routing. Alongside that headline change, it graduates the extensions framework to first-class status, introduces MCP Apps for server-rendered UI, formalizes the Tasks extension for long-running work, adds production-grade observability headers, upgrades to full JSON Schema 2020-12, and hardens OAuth 2.0 authorization through multiple SEPs. Three features — Roots, Sampling, and Logging — are deprecated under a new lifecycle policy with a one-year sunset window.