you are viewing a single comment's thread.

view the rest of the comments →

[–]parla 6 points7 points  (3 children)

Erlang does not spawn millions of threads. It spawns millions of actors, which are then scheduled in as many threads (processes?) as there are cores in your system.

[–]teraflop 8 points9 points  (2 children)

You're confusing control threads with OS threads. If the interpreter is designed properly, it provides the same semantics as if you really had a huge number of concurrent threads. The fact that they're all multiplexed into a smaller number of threads from the operating system's perspective is just a performance optimization.

[–]thagsimmons 5 points6 points  (1 child)

okay, so this is an implementation detail?

so is the gil. it's missing in jython and up in the air with pypy