Author here. Thank you for the link to Midori's error model. It's on my reading list for this week. > So we should keep the door open, and not pretend we have

Author here. Thank you for the link to Midori's error model. It's on my reading list for this week. > So we should keep the door open, and not pretend we have already solved errors. Very much this. Even with errors as values, the approach languages like Go take makes composition difficult. I presented the Kleisli approach instead. That recovers compositionality. OCaml does something I find interesting. It makes exceptions performant by not capturing stack traces by default. But it's still too easy to forget handling the exception. > btw, the article uses Rust, not Go, but anyway... I actually used TypeScript. The Rust bit was meant to introduce the idea from Rust to TypeScript. It's not new in TypeScript, but it's not popular either. I have updated the article to clarify that.