A favorite HN comment that discusses this: https://news.ycombinator.com/item?id=13503951 https://news.ycombinator.com/item?id=13503951 Go read it all but here'

A favorite HN comment that discusses this: https://news.ycombinator.com/item?id=13503951 https://news.ycombinator.com/item?id=13503951 Go read it all but here's a relevant quote: """ So how does Erlang ensure that processes don't hog a core forever, given that you could theoretically just write a loop that spins forever? Well, in Erlang, you can't write a loop. Instead of loops, you have tail-calls with explicit accumulators, ala Lisp. Not because they make Erlang a better language to write in. Not at all. Instead, because they allow for the operational/architectural decision of reduction-scheduling. """