• Sources: primary, discussion
  • Summary: The 2026-09-24 post from Carl Lerche and Julien Scholz publishes Topcoat v0.9 and describes the rendering model in code, where browser-side signals can be read while rendering on the server and only the shards that track a changed signal re-run, morphing the returned HTML to preserve focus and input state. The live! and emit! macros emit repeated UI updates, and 0.9 extends that past the initial page load to a WebSocket the server pushes over. Toasty, the framework's ORM, gains an update! macro that issues a single statement, #[document] fields encoded as PostgreSQL JSONB with filtering pushed into the query, and polymorphic relations expressed as an enum with a shared key column.
  • Why it matters: The post argues that framework conventions reduce token use and error rates for coding agents, which is an author-stated position rather than a benchmark, so a team weighing the framework has to measure that claim itself.

send feedback on this story