News for hackers. Stuff that matters.
Re:Node.js - A Giant Step Backwards by sausagefeet on Thursday August 04, 2011 @08:58PM (#2848514)
Nitpick: Node doesn't do anything in parallel, it can't, it does things concurrently.
Re:Node.js - A Giant Step Backwards by IbJacked on Thursday August 04, 2011 @09:19PM (#2848568)
But, um, concurrently means "at the same time," too. Merriam's first definition is actually "running parallel."

Wouldn't it be better to describe it as running serially, using non-blocking asynchronous function calls? Guess that doesn't really roll of the tongue, though.

Re:Node.js - A Giant Step Backwards by sausagefeet on Thursday August 04, 2011 @09:29PM (#2848590)
In computer science the two terms are generally distinguished, while you're free to redefine them commonly when people say concurrency they refer to a model of performing things at the same time but may not actually be simultaneous. Parallelism is generally the actual act of it running simultaneously.
Re:Node.js - A Giant Step Backwards by IbJacked on Saturday August 06, 2011 @01:50AM (#2853179)
Fair enough, I was unaware of the common distinction in the CS domain.
Re:Node.js - A Giant Step Backwards by randylahey on Thursday August 04, 2011 @09:52PM (#2848650)
Nitpick: Incorrect. Node.js uses a thread-pool to run things which are necessarily blocking, such as some POSIX functions.
Re:Node.js - A Giant Step Backwards by gcr on Thursday August 04, 2011 @10:55PM (#2848794)
sausagefeet meant we can't get to that thread pool from user code.
Re:Node.js - A Giant Step Backwards by Fenn on Thursday August 04, 2011 @09:02PM (#2848524)
Hmm, nice spot. Incorrect assumption of synonyms on my part.