Post #1953786
2026-04-20 06:38 UTC
@r I don't think Rust's form of async and what I had to do to shove completion-based IO into it is necessarily a bad thing for high-level usage in Rust, but it's further from what WebUSB wants in JS, so I see why you went that route.
Replies (1)
-
@r@glauca.space 2026-04-20 06:43
@kevinmehall from what i understand, this might not be a "rust async" issue so much as an "existing rust async frameworks" issue (Waker is... a completion!) but yeah, completions-->message-passing-->JS was definitely "simpler"