3 ms·
I agree with some of the technical things that he is saying (though he's several years late to this conversation), but saying things like, "This provides 90% o
by hacknat 12y ago
I agree with some of the technical things that he is saying (though he's several years late to this conversation), but saying things like,
"This provides 90% of the benifits [sic] of parallelism for the common use case without presenting the developer with additional complexity."
is disingenuous. Where does your "90%" come from? Just say, "a lot of benefits" or "many benefits".
Moving onto the question of analogizing human thought as non-blocking versus threaded is tortured and distracting from any main point someone might make.
It is a lot easier for human beings to write code in nodeJS without f*ing themselves over, but that isn't necessarily the case because people understand any better what's happening underneath the covers (do really understand what epoll, select, or kqueue are actually doing at the kernel level?). It's because node's paradigm simply prevents you from being stupid with IO.
You can still be stupid with node though. Back to the "90%" claim, quite a bit of parallelism is used to make computation faster. Node can sometimes still provide some game when computation is a bottleneck. However, since you have to serialize and de-serialize in and out of v8 when you need to thread if you're doing a lot of large computations with large data-structures then node sucks.
- jondavidjohn 12y agoPoint taken on the 90%, updated the post. I don't think anyone is saying node is aways awesome and never sucks, I am just pointing out that it solves one of the most common problems with network/web applications. Which you also point out, (the platform) "being stupid with I/O".
- hacknat 12y agoFair enough.