News for hackers. Stuff that matters.

A comment on Node.js Foundation and JavaScript Foundation Announce Intent to Merge. Parent comment

Re:Node.js Foundation and JavaScript Foundation Announce Int... by frutiger on Thursday October 04, 2018 @10:01PM (#18145173)
> With node, any IO is moved to a new thread

Not quite (or somewhat): the IO is done asynchronously. You tell the kernel to notify you when any of a set of FDs are ready for reading/writing, and it resumes you when that is so.

[ Parent | on HN ]
Re:Node.js Foundation and JavaScript Foundation Announce Int... by hajile on Thursday October 04, 2018 @10:55PM (#18145400)
My understanding is that libuv creates a threadpool that it uses for IO operations and these inform the main thread when an IO event is ready. Is there something wrong with my understanding?
[ Parent | on HN ]
Re:Node.js Foundation and JavaScript Foundation Announce Int... by spiralx on Monday October 08, 2018 @10:52AM (#18167978)
You're both right, although you more than the other guy being a dick. libuv uses a thread pool for asynchronous I/O for everything but network requests, which are handled on the main thread - presumably because they're already asynchronous by nature.

http://docs.libuv.org/en/v1.x/design.html

[ Parent | on HN ]
Re:Node.js Foundation and JavaScript Foundation Announce Int... by frutiger on Saturday October 06, 2018 @12:58AM (#18153611)
Yes there is something wrong with your understanding.

I recommend reading epoll(1) or kqueue(1).

[ Parent | on HN ]