Looking to spread Node "everywhere," proponents are pushing for increased adoption across servers and the desktop as well as the internet of things, according to a presentation by Rod Vagg, member of the Node Technical Steering Committee, at this week's Node Summit conference in San Francisco.
Node developers endeavor to improve stability of Node releases, Vagg said. "Unfortunately, this branch that we have called 'current' -- we used to call it stable -- is not quite as stable as we'd like to be," he said. Too many breakages and regressions have been slipping into releases, he said, and while the situation is not "terrible," it needs improvement.
Planned language enhancements include Zones, which make it easier to write asynchronous code. Threaded workloads, meanwhile, could be implemented in Node akin to browsers supporting Web Workers, which run web content in scripts in background threads.
Node also may see a shifting philosophy related to its use of HTTP, including adherence to HTTP/2. New APIs may be needed for HTTP/2, though, and Node's loose approach to HTTP has been a source of security issues.
To further address security, Node's developers want to clarify and have strict adherence to security policies for Node while supporting a growing ecosystem of security service providers, including Lift, Node Security, and Snyk. Node has faced security issues like denial-of-service and out-of-bounds vulnerabilities recently.
This story, "The future of Node.js: Stable, secure, everywhere" was originally published by InfoWorld.