Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

For those interested to learn more about Go's handling of async, I wrote a comment a while ago where I describe why I too think the Go model is superior: https://news.ycombinator.com/item?id=27545031

EDIT: Superior for most non-performance sensitive use cases, that is.



I personally prefer Go's handling of async too. I'm not sure if I would call it superior, because from what I understand monadic async has its uses, especially when you don't have a runtime. But for the kind of programming that I do, which doesn't need every last bit of performance, monadic async is a pain.

For people not familiar with "monadic async", it's the formal way to refer to the function coloring problem [1]. Monads offer you ways to "lift" your functions/values in the monadic world (paint the blue values red), but you can't do the opposite (paint the red functions/values blue).

[1]: http://journal.stuffwithstuff.com/2015/02/01/what-color-is-y...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: