News for hackers. Stuff that matters.

A comment on Node.js Flow – Callback Hell vs. Async vs. Highland Streams. Parent comment

Re:Node.js Flow – Callback Hell vs. Async vs. Highland Streams by ZitchDog on Wednesday January 28, 2015 @07:35AM (#8959424)
Because node is single threaded, so blocking for this user will block all requests for all users.
[ Parent | on HN ]
Re:Node.js Flow – Callback Hell vs. Async vs. Highland Streams by BonoboBoner on Wednesday January 28, 2015 @01:13PM (#8961471)
That explains it, thanks. To me this makes the focus on non-blocking code in PlayFramework2.0 a bit more strange to me, since the JVM isnt single threaded.
[ Parent | on HN ]
Re:Node.js Flow – Callback Hell vs. Async vs. Highland Streams by yowmamasita on Wednesday January 28, 2015 @02:36PM (#8961991)
it's because native threads are expensive
[ Parent | on HN ]
Re:Node.js Flow – Callback Hell vs. Async vs. Highland Streams by BonoboBoner on Thursday January 29, 2015 @02:11AM (#8964760)
They are again? In this talk they mentioned them to be cheap in 2008
[ Parent | on HN ]