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.

The DuckDB-WASM + OPFS announcement on September 18, by Carlo Piovesan and Geertjan Wielenga, is the kind of headline that reads like a novelty — an analytical database engine, compiled to WebAssembly, persisting to a real file system inside a browser tab. But the novelty isn't DuckDB. It's the platform layer underneath it. Over the last few years the Origin Private File System (OPFS) quietly turned the browser into a place you can run a real database, not just a cache with delusions of grandeur. The interesting question isn't "can DuckDB do this?" — plenty of engines can now. It's what changed at the platform layer to make any of them possible, and whether your project should care.

What caught our eye this week across JavaScript Weekly #802, React Status #491, and Node Weekly #641 — and what it means for the Aliz stack.

React 19.3 shipped on September 9, 2026. Two APIs that have been sitting in the experimental drawer since the April 2025 React Labs post — <ViewTransition> and Fragment Refs — are now stable, joined by a browser() escape hatch for SSR, Trusted Types passthrough, and Context rendering in Server Components. There are no breaking changes, no deprecations, no codemods, and no upgrade guide, because none are needed. The interesting question isn't whether to bump the version. It's which of these APIs earn a place in your codebase.

What caught our eye this week across JavaScript Weekly #799, React Status #488, and Node Weekly #638 — and what it means for the Aliz stack.

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.

What caught our eye this week across JavaScript Weekly #796, React Status #485, and Node Weekly #635 — and what it means for the Aliz stack.

The State of CSS 2026 results are out, fielded May 15 – June 29, 2026 with ~4,900 respondents. The question set shrank from 63 features to 46, and the headline is a contradiction: the most-wanted new feature of the year is also the most-avoided one. Underneath that sits something stranger — CSS is the one part of the frontend stack AI still can't write. This post is about what to do differently, not about what the charts say.

This is my token telemetry for July 2026 — one developer's month, pulled from the Aliz AI usage dashboard. Earlier this month I wrote You Don't Deserve Fable (Yet), which argued that routing discipline comes before reaching for the biggest model on the menu. This post is a month of receipts for that argument, including the parts where I plainly haven't applied my own advice. It's also a mixture of before and after: the routing discipline was still forming while the month ran, so this isn't a steady state. Some of the chart describes habits I'd already changed, and some of it describes habits I was in the middle of changing.

What caught our eye this week across JavaScript Weekly #795, React Status #484, and Node Weekly #634 — and what it means for the Aliz stack.