egghead.io developer chats

The episode contains several genuinely technical nuggets - full-stack signals across client-server, the IVM+Solid reactivity synergy, and Vite 6 unlocking Cloudflare local dev - but they are buried under extended personal anecdotes about a fitness app, AI vacuum metaphors, and rambling meta-commentary. Insight-per-minute ratio is low.

“What I was doing with signals was trying to make them full stack, so make them work across the boundary. So you have a stateful server, something like a durable object, and you can define these reactive like signals and uh, derivations on the server, and you just pass them to the client and the client listens to them.”

“Solid can take that a step further and see that, okay, this is one tiny piece that has changed in the data. I need to make this one tiny change in the UI and I'm done.”

The full-stack signals concept is genuinely novel research work, and the analysis of why React's Suspense never penetrated its own ecosystem is a sharp, underappreciated framing. The AI-coding and OOP tangents are entirely recycled territory.

“instead of being stateless server components like React, these are stateful server components. Which means instead of rerendering the whole thing, sending the entire payload, the server can just update one piece of one node there”

“it was kind of pioneered by uh, Milo, who again he was on the solid Core team because he experimented with signals in a way where you can kind of have, uh, this implementation that can work in any different framework”

Speaker B is a legitimate practitioner - active SolidJS core team member doing original signals research that won a $7,000 hackathon - with real depth on framework internals. Speaker A is a competent educator but not a domain authority, and both speakers spend significant time outside their zones of expertise.

“This project actually won solid hack, uh, $7,000, uh, which was very nice.”

“since I joined the SolidJS core team, I've been looking a lot, a lot more into like the internals of its like reactivity system.”

There are named specifics - SolidHack prize, Vite 6 resolving Miniflare/SSR mode conflicts, specific libraries (Relay, React Query, Apollo), React Miami as the origin of Zero Sync - but many key claims are asserted without evidence and the AI-coding discussion is almost entirely anecdote-driven.

“if you're using Relay, you can use Suspense, or you probably have been using Suspense. If you've been using Apollo maybe, uh, if you're using React Query, you're probably not using Suspense.”

“with Vite, you run it in SSR mode and it just runs node. So if you have a Vite project that you want to test with Miniflare, with like your local, uh, Cloudflare runtime, it was basically impossible to set that up.”

The host lands one genuine push-back (XML vs JSON token efficiency) and a few decent framing questions about React's scale problem, but also spends several minutes narrating his personal fitness app in screencast mode, asks 'Anything else you're excited about?' as a closer, and routinely lets technical claims pass unchallenged.

“Why do you have that context and those prompts in an XML file? I haven't seen an XML file in forever. Why XML?”

“You think it's like a scale issue with React. Like it's just like a glacier in terms of its movement versus Solid”