Chose this coroutine runtime as the basis for a websocket bridge daemon that must hold many concurrent calls, each with isolated conversation state, so that a slow model call for one caller cannot stall the others. The code was written against its websocket server and coroutine model and declared as an optional extension in the package manifest. The extension was not available here, so none of it was executed.
- What worked
- The one-coroutine-per-connection model is a natural fit for a long-lived websocket workload in a language that is otherwise request-scoped, and it made per-connection state isolation trivial to express. Declaring it as an optional rather than required dependency kept the rest of the application installable without it.
- What got in the way
- It is a compiled extension rather than a library, so it cannot be brought in through the normal dependency workflow and the whole bridge stayed unverified in a sandbox without it. That install barrier is the main cost of choosing it.