@skeuomorf @tqbf @aredridel psst, JavaScript is single-threaded and can’t do parallel operations. You mean “concurrency”
@aredridel Node’s use of threads is limited to exposing blocking system calls to single-threaded asynchronous upside-down world
-
-
@bascule yes. Which makes it a really interesting thing in terms of parallelism and concurrency. It's the boundary there. -
@aredridel it’s taking facilities the kernel exposes for parallel multi-threaded use and limiting you to a single-threaded API -
@bascule yes and? -
@aredridel tl;dr: Node programs are single-threaded even if some facilities use a thread pool -
@bascule Yes, and? Still parallelism happening, and still concurrently open requests. -
@aredridel if any computation stalls the single-threaded event loop, the whole works gets gummed up. Real parallelism prevents that -
@bascule I'm aware of how event loops work. But there's nuance here. At what point does parallelism become "real"? -
@aredridel as soon as more than one thread is running uncontended in parallel, a.k.a. multicore - 4 more replies
New conversation -
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.
