Hacker News new | past | comments | ask | show | jobs | submit
Tangential, but since the thread is all DOM: I've been using Solid 2's universal renderer for native watchOS UIs, and just put the renderer and host up as an MIT repo: https://github.com/esensible/solid-watch

The bundle (Solid JSX compiled with the new babel plugin) runs in QuickJS-ng on the watch; the renderer emits node mutations over a small host interface; a Swift host lays them out with Yoga and draws with SwiftUI. The same bundle runs in a browser harness for development. The structure is borrowed from React Native's Fabric: three trees, batched commits, one schema that generates the prop code for both sides. A dozen node types, React Native style names, on purpose.

For context, it's the display layer of a larger personal project (not open source at this point): application state lives in a small expression language with a Rust evaluator, running on the phone or on an ESP32 box, with the state, events and view described by JSON Schemas and a schema-derived wire codec. The watch and an e-ink display are synced views of that state. Bundles and firmware are served and updated over BLE, and the phone app has a sign-in-with-ChatGPT authoring mode that writes the Solid UI and the expression logic against those schemas, checks them on the device, and packs the bundle locally on the phone, no server. Solid's universal renderer is what made the watch part feasible: the UI author writes ordinary JSX and the same bundle runs on the wrist and in a browser tab.

Rough edges in the public piece: you build the QuickJS xcframework yourself, and getting a bundle onto a real watch still means an Xcode build. Examples built with plain npm and the browser harness are in the repo if you want to poke at it. Moving from the RCs to 2.0.0, the only breaking change I hit was <Show> compiling to a ternary, which only reordered mutations inside a commit.

loading story #50541284