3 ms·
What Erlang does is have each "thread" (they're really called processes and they're neither system processes nor system threads, but Erlang processes) have a lo
by davidw 17y ago
What Erlang does is have each "thread" (they're really called processes and they're neither system processes nor system threads, but Erlang processes) have a loop that sends data back to itself with whatever modifications may have been requested by the user, thus simulating a variable with state, to some degree. It also does have per process ways to just plain store data, but they're severely frowned upon.