@bascule yes. Which makes it a really interesting thing in terms of parallelism and concurrency. It's the boundary there.
-
-
Replying to @aredridel
@aredridel it’s taking facilities the kernel exposes for parallel multi-threaded use and limiting you to a single-threaded API1 reply 0 retweets 1 like -
Replying to @aredridel
@aredridel tl;dr: Node programs are single-threaded even if some facilities use a thread pool2 replies 0 retweets 0 likes -
Replying to @aredridel
@aredridel if any computation stalls the single-threaded event loop, the whole works gets gummed up. Real parallelism prevents that2 replies 0 retweets 0 likes -
Replying to @aredridel
@aredridel as soon as more than one thread is running uncontended in parallel, a.k.a. multicore2 replies 0 retweets 0 likes -
Replying to @aredridel
@aredridel Node is single threaded. Anything that stalls the event loop prevents I/O processing. There is no parallelism.3 replies 0 retweets 0 likes
@aredridel there are ways to do do parallel processing in JavaScript, e.g. SIMD.js: https://hacks.mozilla.org/2014/10/introducing-simd-js/ …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.