Maybe that's just marketing, but it's really intriguing how human best practices are also agent best practices; how, maybe, we've reached a point where even devs aren't recognizing agent best practices as human best practices anymore; and how suddenly best practices are being prioritized in a way they often weren't - humans could/would/were expected to suck it up and deal with poor devex, but agents simply can't. A strange sort of victory for us folks who cared about it.
Solid's solution here is beautiful. The server RPC and 'live' and 'broadcast' are seamless, and feel much more natural to use than liveview or htmx/datastar imo.
My counter component bundle test is:
4.8 KiB (brotli'd) in Solid v1.9.18
20.3 KiB (brotli'd) in Solid v2.0.0It just feels like the right way React should be.
Honestly, I was probably just so tired of React that it felt refreshing to develop in something so un-React-like, and it ergonomically felt better at the time than writing something similar to React via Solid, even if the latter was still holding its own in performance on paper. If you've spent years learning French then it might feel more refreshing to start learning Japanese than Italian.
It turns out Solid had a lot of it right all along. And after using Svelte for a while, something starting feeling... weird. For all its complexity, something I always appreciated about React was that I was ultimately just writing JavaScript, and with Svelte it felt like I was writing in something only made to resemble JavaScript.
I still really appreciate Svelte, but I'm wondering if this would be a good time to see if Solid will feel more "natural" to me, having worked with JavaScript all these years. Curious if anyone can confirm if that would be the case.
Now might also be a good time to tinker with it myself before the coding models are fully up to date on 2.0 and I turn to laziness (/efficiency) and have them handle the rest.
They all convinced me to use their respective languages by sharing all the thought they put into them, especially to address problems in the alternative, more popular options.
I didn't like it then either.
I much prefer Solid over React, but at least the idea of a compiler makes so much more sense instead of manually maintaining memoization.
Contrast that with React, where hooks are colored functions. You thought that hooks were just functions? Nope, if you have a hook, it MUST be called in a hook/component... exactly like async. Did you want to load this TTS player conditionally? Hahah, you can't. Have fun allocating memory for every TTS provider your app supports, even if the user uses only 1 player. https://news.ycombinator.com/item?id=45257413
"Thanks to async in the graph we can detect waterfalls, poorly constructed effect loops, poorly scaling graph shapes like wide graph fanouts and fan-ins." Incredibly cool. Apparently Tanstack Query has a waterfall detector https://github.com/bamlab/tanstack-query-detect-waterfall so the other frameworks have something similar, but it won't work with their state graphs.
That needs to emphasized more. Pretty sure React's Suspense suffers from waterfalls if memory serves.
I think with the advent of AI it doesn't matter so much about the DX and your main focus should be on better UX (the best lighthouse metrics) though I don't think their DX is bad either.
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.