4 ms·
Not sure if you read it fully or not: > When Node.js became popular, it was the first major framework to embrace a nonblocking programming model which made it
by manojlds 6y ago
Not sure if you read it fully or not:
> When Node.js became popular, it was the first major framework to embrace a nonblocking programming model which made it very efficient for IO-heavy tasks. (We mentioned this in our write-up of Node.js in 2012.) Due to its single-threaded nature, Node.js was never a good choice for compute-heavy workloads, though, and now that capable nonblocking frameworks also exist on other platforms — some with elegant, modern APIs — performance is no longer a reason to choose Node.js.
- orange8 6y agoI did read it, just looks like I failed to fully parse that long winding sentence. So it is not a good choice for compute-heavy workloads, like a webapp that does video/image processing? Multi-threading could be added to the runtime for back-end applications (https://news.ycombinator.com/item?id=15498219 https://news.ycombinator.com/item?id=15498219)