I specifically mentioned that in my comment. Yet, in languages that do have the concept of a thread (and do not restrict side effects), these are all anti-patterns: performing side effects in these monadic compositions is dangerous, and those compositions replicate constructs that already exist in those languages (control structures, exceptions). No one in their right mind would consider importing these Haskellist concepts to other languages were it not for the fact that blocking threads is expensive. Fixing that problem directly -- meaning, making blocking free -- is therefore the right solution.
Functional programming and async I/O in single-threaded languages are closely connected. Functional programming has no built-in notion of time; conceptually, the time a pure function takes to run must not have any effect on correctness, or replacing a function call with its value would have side-effects. To allow time to pass in a way that matters for correctness, you need callbacks, and monadic types are a form of callback-based programming. In a single-threaded program, the goal is for functions to execute as quickly as possible so that the user doesn't notice pauses, so the solutions end up being similar.
So these are not implementation tricks; they're fundamental to the theory of how programs execute. Erlang is built on callbacks as well since each event results in another function call.
Goroutines and blocking function calls are fundamentally different. Blocking function calls need to return at the right time or it's a bug.