this is great. the clear definitions for italicized words are great. Multiple new learnings for me here

• Examples of prior art and how they classify would be helpful (e.g. example of a synchronous vs async system). • I propose linking a new page "functional effect system" (I have an unpublished article about this that you could use as a starting point) • propose to link to your 2021 talk about supervision?

@U09K620SG does it answer your questions about coroutine scheduling ?

i am surprised, because > user code evaluation is never implicitly transferred to another thread this is what intuitively makes sense and what I expected, but the behavior i was observing, as i understand it, was the coroutine transferring threads actually, as demonstrated by *out* changing values when using println inside a flow which booted at the REPL. The first println goes to the repl and subsequent printlns go to stdout (i.e. are not intercepted by the REPL which rebound out away from stdout to the REPL )

i don't understand this one, a clear definition of "operator" in the first sentence would help. Perhaps also a conclusion sentence that summarizes the lesson

"Compare this behavior with future" I would prefer that not to be an exercise for the reader