Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Node.js goes pro: New opportunities -- and risks

Serdar Yegulalp | Feb. 13, 2015
The meteoric rise of Node.js means greater scrutiny of tools and shortcomings in the years ahead.

Joyent's plans to address this became clear only recently. Version 0.12 of Node was finally delivered in February 2015 with improvements in the above vein, and a separate Node.js Foundation is being set up to move governance to a disinterested third party.

Before that, however, others took their own steps. A fork of the Node.js project, named io.js, came into being as a way to address debugging, slow release cycles, and governance, among other issues.

Other plans include adding tracing functions to Node.js on Linux, and using a more recent build of the JavaScript V8 engine to "integrate with the latest debugging tools Google has made for Chrome and take advantage of other work they've done to improve debugging."

"Debugging has always been challenging in an async environment," said Rogers, "but we're making headway."

Io.js is still young, although a few existing Node.js deployments have already switched over to it (Uber is one of the more prominent organizations to do so). But whether those advances and more like them come from Io.js or Node.js itself, it's clear that changes are badly needed for Node.js to flourish even more.


Previous Page  1  2  3  4 

Sign up for CIO Asia eNewsletters.