@skeuomorf @tqbf @aredridel psst, JavaScript is single-threaded and can’t do parallel operations. You mean “concurrency”
@aredridel @tqbf it’s an important distinction, IMO. @skeuomorf thought so too at least 
-
-
@aredridel@tqbf as@skeuomorf pointed out,@rob_pike has an entire talk dedicated to the subject: https://www.youtube.com/watch?v=cN_DpYBzKso … -
@bascule yeah, though if you actually look at what is going on, it is parallel, implemented with a thread pool. -
@aredridel curious where Gulp keeps its thread pool… all I found was this: https://github.com/gulpjs/gulp/issues/317 … -
@bascule not gulp. Node. -
@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? - 9 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.