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.
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.
Comments
Nitpick: Node doesn't do anything in parallel, it can't, it does things concurrently.
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.
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.
Fair enough, I was unaware of the common distinction in the CS domain.
Nitpick: Incorrect. Node.js uses a thread-pool to run things which are necessarily blocking, such as some POSIX functions.
sausagefeet meant we can't get to that thread pool from user code.
Hmm, nice spot. Incorrect assumption of synonyms on my part.