FAQ
hi,
these are real problem in nodejs or misconceptions please comment
a) It is not multithread; therefore your X number of CPU cores will never
get utilize ... no scalability at all.
b) Since every IO operation is done via handler therefore no stack trace
... how would you be able debug such scenario.
c) Since IO operations are async ... doing multiple IO will get your
handlers nested in another each other ... hence very ugly code to read and
understand

--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Search Discussions

  • Mark Hahn at Oct 17, 2012 at 9:20 pm
    Those are valid concerns. There are workarounds for each of them. Also
    the benefits outweigh the problems.
    It is not multithread
    This is the whole point of node. Avoiding threads is good. You can use
    multiple cores by the cluster feature which works very well for apps that
    take multiple requests.
    hence very ugly code to read and understand
    Not after you get experience. It reads very naturally to me after coding a
    week or two. It is a much easier shift of thinking than something like
    going to lisp. There are also several solutions that let you write the
    code in a serial manner.
    Since every IO operation is done via handler therefore no stack trace
    Several of the solutions mentioned in the previous question can also fix
    this.

    If you google nodejs you will see hundreds of discussions about these
    issues.
    On Wed, Oct 17, 2012 at 11:49 AM, vicky mac wrote:

    hi,
    these are real problem in nodejs or misconceptions please comment
    a) It is not multithread; therefore your X number of CPU cores will never
    get utilize ... no scalability at all.
    b) Since every IO operation is done via handler therefore no stack trace
    ... how would you be able debug such scenario.
    c) Since IO operations are async ... doing multiple IO will get your
    handlers nested in another each other ... hence very ugly code to read and
    understand

    --
    Job Board: http://jobs.nodejs.org/
    Posting guidelines:
    https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
    You received this message because you are subscribed to the Google
    Groups "nodejs" group.
    To post to this group, send email to nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/nodejs?hl=en?hl=en
    --
    Job Board: http://jobs.nodejs.org/
    Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
    You received this message because you are subscribed to the Google
    Groups "nodejs" group.
    To post to this group, send email to nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/nodejs?hl=en?hl=en

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupnodejs @
categoriesnodejs
postedOct 17, '12 at 9:03p
activeOct 17, '12 at 9:20p
posts2
users2
websitenodejs.org
irc#node.js

2 users in discussion

Mark Hahn: 1 post Vicky mac: 1 post

People

Translate

site design / logo © 2022 Grokbase