Re:JavaScript Fatigue or My History with Web Development
by ousta on Tuesday June 27, 2017 @05:59AM
(#14643758)
Yeah Clearly NODE.JS was not picked because it's cool but because of its single threaded poor performance (talking about the cool years of node.js)
[ Parent
| on HN ]
Re:JavaScript Fatigue or My History with Web Development
by ralusek on Tuesday June 27, 2017 @11:48AM
(#14646491)
Compared to Python or Ruby, NodeJS has phenomenal performance. The single threaded argument is also flat out wrong, given that you have clustering or web workers to take advantage of every core. It's also completely misleading even within a single core, as non-blocking nature of JS will accomplish on a single core what otherwise behaves as threading would.
Re:JavaScript Fatigue or My History with Web Development
by ojr on Tuesday June 27, 2017 @06:47AM
(#14644056)
the cool years of node are just beginning with AWS Lambda and other cloud services that help node.js scale easier
Re:JavaScript Fatigue or My History with Web Development
by tobltobs on Tuesday June 27, 2017 @09:34AM
(#14645206)
Wait, maybe I am dumb, but why do you need AWS Lambda to scale Node.js better? You use something like Lambda which is build to handle one request per instance to scale something which is single threaded anyway?
Re:JavaScript Fatigue or My History with Web Development
by fenwick67 on Tuesday June 27, 2017 @12:19PM
(#14646763)
Say I have an endpoint that has to parse a giant JSON object, which can take 100ms to parse... if that locks the thread it can block another request. With lambda I would just make one lambda function for each route and routes won't block each other.