Good news! I don't need callbacks to implement signals, between components. I can use streams, which are upcoming in WASI 0.3.
Holobrine
>wants to make a UI engine centering wasm instead of JS >wants to use component model >needs callbacks to implement signals >WASI does not support callbacks because of JS scope chains >wasm does not free us from JS, sad
Aug 28, 2025 at 4:27 AM
How to represent callbacks in WASI? · Issue #669 · WebAssembly/WASI
I'm looking to create a Signal engine like how SolidJS works, with a WASI interface. The way Solid handles dependency tracking is the provided callback is called once during declaration and the...
Defining client callback type in WIT · Issue #223 · WebAssembly/component-model
I'm trying to define a component interface in WIT format so that components (client) can pass callbacks (closures) to host. Host can then store the callback somewhere and then invoke the callba...
Beyond Signals, by Ryan Carniato
Components in Markdown
Fast, streaming-ready markdown parser with Vue, React, and Svelte component support. Parse Comark content from strings or streams with TypeScript support.
Streaming responses with tool calling· Ollama Blog
Ollama now supports streaming responses with tool calling. This enables all chat applications to stream content and also call tools in real time.
WaveringAna/atproto-ui
A React component library for rendering common AT Protocol records for applications such as Bluesky and Leaflet.
React 16.x Roadmap – React Blog
This blog site has been archived. Go to react.dev/blog to see the recent posts. You might have heard about features like “Hooks”, “Suspense”, and “Concurrent Rendering” in the previous blog posts and talks. In this post, we’ll look at how they fit together and the expected timeline for their availability in a stable release of React. An Update from August, 2019 You can find an update to this roadmap in the React 16.9 release blog post. tl;dr We plan to split the rollout of new React features…
More Actors with Tokio
In spring 2021, when I was first submerging into tokio, a colleague and friend mentioned I should ingest this article: Actors with Tokio by Alice Ryhl. And, did I ingest it. To summarize, the article proposes an architectural style which relies on message passing (channels) and inherent parallelism (tasks) as well as concurrency (via async/.await) to neatly and safely structure applications dealing with I/O. But really, go read the article.
Composing Time: Compositional Async in Solid 2.0
mitchellh/libxev
libxev is a cross-platform, high-performance event loop that provides abstractions for non-blocking IO, timers, events, and more and works on Linux (io_uring or epoll), macOS (kqueue), and Wasm + WASI. Available as both a Zig and C API.
Instant & Feeless— Flash Channels
Update: Flash channels are deprecated in their current state. We aim to reintroduce Flash Channels as a part of future GoShimmer milestones. For more information look at our docs [https://docs.iota.org/]. -------------------------------------------------------------------------------- The goal of the IOTA Foundation is it to build a flourishing Machine Economy, where machines
Overview — atex v0.9.1
Looking to use a data subscription service like the Firehose, Jetstream, or Tap? Check out Drinkup.
Rendering AT protocol posts on my /feed
I’ve got the data, so now it’s time to wire that up to Astro and the wider components system.
