Ever considered using Node.js for CPU-intensive computing? If so, you must be aware that it is not the best way to go. This, however, may change in the future as a new face of Node.js is appearing on the horizon.
The latest news from Node.js community makes us think that this is about to change in the near future. The 10.5.0 release has announced multithreading in Node.js. The feature is still experimental and likely to undergo extensive changes, but it does show the direction in which Node.js is heading.
Why would Node.js, boasting about it being single-threaded, now implement a feature that is quite contrary to its fundamental assumption? My idea is that once multithreading is fully functional, Node.js applications will benefit from both single-threading and multi-threading. In other words, Node.js will remain single-threaded, unless it’s decided otherwise to suit specific business requirements. Finally, Node.js will give room for graphics, complex data processing, and machine learning.