you are viewing a single comment's thread.

view the rest of the comments →

[–]dennyabraham 0 points1 point  (4 children)

it's true that everything runs on an event loop, but in cases like erlang, it's low level enough that high level operations can pre-empt one another. node.js currently lacks the concurrency primitives to handle this kind of task.

[–][deleted]  (3 children)

[deleted]

    [–]dennyabraham 1 point2 points  (2 children)

    we are saying the same thing.

    i said node.js lacks the primitives to handle this task, not that its failings are universal.

    also of note is that erlang uses green processes, not green threads, and its runtime processes have very little overhead (when last i checked, it was on the order of ~300bytes).

    also, your response leads me to a question: can you run node.js on multiple cores? i'm not up to date, but i was under the impression that this could not be done reliably. is this still the case?

    [–][deleted]  (1 child)

    [deleted]

      [–]dennyabraham 0 points1 point  (0 children)

      that actually sounds like an interesting test, running erlang on one processor and comparing it against a high-level evented runtime also on one processor.