Rambling about the new Block composition model and TEA scalability and sharing some before/afters on the Foldkit docs site (which is a Foldkit app of course). (Sorry bout the camera window positioning)

Foldkit’s Blocks + Effect Layers preview release is incoming. Should be ready within the next few hours. (This is a test of whether 6.1 Sol gets it over the finish line or stalls waiting for user input. The user will be asleep.) Preview status and installation instructions are in the PR description. Feedback greatly appreciated! ❤️ github.com/foldkit/foldkit/p…

Goal is to get the preview release I’ve been teasing out tomorrow (Saturday). Posting for accountability :) The new APIs will be good. The docs (for the preview release) will be unreviewed slop. Better to get it out though! Quick overview: The architecture will stay the same. The way you compose the pieces (Model, Message, update, view, Commands, Subscriptions, etc.) will change. The new Block primitive replaces Submodel. Think of a Block as a mini Foldkit program. Parent Blocks bind child Blocks and define how they connect, like a socket and plug. This streamlines a lot of the boilerplate you see in larger Foldkit applications. Block provides more explicit structure for how your application fits together, which feels very “Foldkit” to me! Type inference is a lot better. Instead of repeatedly annotating Model and Message types, you define a Block in one place with its Model and Message Schemas, then use that to create the other pieces of the Block (update, view, etc.). It reads quite nicely! Sharing the counter example here to give you a sense of the new APIs. This doesn’t show off all the cool new Block stuff, but it does (I hope) show how things have been streamlined. There’s a lot more, but this message is already long and it’s nearly 2 AM, so I’ll leave it there for now. Thanks!

Foldkit + Cloudflare Workers docs developers.cloudflare.com/wo…

I think “clean code” is just a bad term. Overloaded, subjective, and purity-coded. One person’s clean code is another person’s slop. What matters today is standardized, highly constrained architecture, where strong conventions enable agent productivity. Your agent should never be deciding between several state management solutions, several UI libraries, several observability tools. For a web application, just use @EffectTS_. Just use @alchemy_run. Just use @foldkit. I think this is the future. Let your agent run wild within a system that ensures architectural sanity and offers powerful, built-in observability, inspectability, and testing capabilities. And there’s no reason agents can’t write code that’s inspectable and understandable by humans. We can have our cake and eat it, too. In fact, verifiability is a requirement in many domains. I’ve worked in security and healthcare, and there’s no way I’m shipping code I can’t verify. I’m responsible if someone gets the wrong medication, or someone with a knife gets through a security checkpoint, because of my code.

Benefits of the CAFE stack (@Cloudflare + @alchemy_run + @foldkit + @EffectTS_) for building software with coding agents: 1. Agents invent less architecture. They focus on product-level execution within a well-defined architecture. You build faster, with more confidence. You focus on what makes your product unique. 2. Your codebase becomes semantically rich. Intent and meaning are explicit rather than left for future agents to infer. Each new agent spends fewer tokens reconstructing intent. 3. Tests read like executable behavioral specs. Expected behavior is easy to inspect, and both humans and agents can verify implementations against it. 4. Strong conventions result in remarkably legible AI-generated code. Agents do what you expect more often, with less steering. The codebase feels consistent and predictable. 5. Explicitness makes behavior clear. Unexpected magic has fewer places to hide. Diffs are easier to review. Yes, it’s more LoC, but who cares when you’re not writing it by hand?

Streaming today at 2:30 PM ET with @maxwellbrown of @EffectTS_ and @samgoodwin89 of @alchemy_run. We’ll be having some fun building with the CAFE stack and probably getting distracted. Come hang out! (will repost with the link)

Foldkit 0.167.0 is now available on everyone’s favorite JavaScript package registry! - SSR without HTML templates - New @​foldkit/node adapter for SSR - VirtualList improvements for chats and feeds - Update keyed Submodels with foldChildAt - Browser Stream helpers moved to the Dom module Details and VirtualList chat demo: foldkit.dev/blog/foldkit-0-1…

@EffectTS_ Boston meetup?!!?! Would love to make it happen. If you’re in Greater Boston and would come (or know of companies in Boston using Effect I can reach out to), reply or DM me so I can get a sense of whether there’s enough interest.

New tagline who dis? ❌ The frontend framework for correctness. ✅ Build faster. Understand what ships.