Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Not OP, but... I'd argue that async style event handling is even more readable then the traditional way of using callbacks. Take a look at this counter example in Async UI (a project I've been working on that's very similar to what OP purposes); my event handlers are all in the same place, and my state (the value variable) is a regular variable; no reactivity primitive needed.
What is the relation and differences between this approach and rust-signals?
They are both async and made for GUI -- in case of rust-signals WebGUI, provided by dominator and MoonZoon.
They are both async and made for GUI -- in case of rust-signals WebGUI, provided by dominator and MoonZoon.
Take a look at crank.js, a JavaScript framework where components can be written as async functions or as generators. It seems similar to what you're trying to do :)