Hacker News Reader

> block the event loop

This is one of the problems Erlang solves: its internal scheduler keeps things running even if some code ends up in an infinite loop or otherwise misbehaves.

View on HN

Infinite loops aren't necessarily a form of misbehavior in Erlang. It is how you keep Erlang processes up after all - just spawn a function that calls itself at the end. Though the vast majority of those have a receive statement so that they're not always running.

Clearly I was not talking about the normal kind of "infinite loop", but the "malicious" sort.

Reply on news.ycombinator.com