Concurrent beam?

[Luke Gorrie]

Ahoy,

Quite often the "the Erlang emulator doesn't exploit SMP" beef comes
up, and it seems like doing a full-blown parallel Pekka-and-Tony-style
emulator isn't on the cards in the near future.

So what I wondered was, in Erlang style, might it be easier to write a
concurrent emulator rather than a parallel one, with one thread per
logically concurrent activity?

For example, one thread executes erlang processes, one garbage
collects, one does I/O, etc?

Just a thought. Lack of SMP doesn't actually bother me in practice.

Cheers,
Luke