Node.js fork io.js hits version 1.0 – but don't call it production-ready

Server-side JavaScript runtime makes major version break

The io.js JavaScript software development runtime, a fork of Node.js, has reached version 1.0, lapping the version numbering of the original project on which it was based.

Prominent Node.js developer Feodr Indutny created io.js in December 2014 after clashing with Joyent, the company that maintains Node.js, over the project's governance model. The io.js project is not managed by any one company, but is instead maintained by a technical committee.

With the release of io.js 1.0.1 on Tuesday, io.js is not only compatible with more than 110,000 Node.js modules (aka npm modules) but also features capabilities not yet found in Node.js, the preview release of which is only on version number 0.11.14.

The io.js developers are quick to point out, however, that the change in version numbering doesn't mean the new release is more mature or stable than Node.js.

"The choice to release as 1.0.x was not to signify that io.js should be considered production-ready, but because it was a significant enough release from Node.js™ to warrant a major version increment," explains a FAQ page on the project's website.

One key advantage of io.js is that the project's developers are committed to running it against recent build's of Google's V8 JavaScript engine. Node.js also runs on V8, but the forthcoming version will only bundle V8 version 3.26.33, while io.js 1.0.1 is built against version

What this means is that io.js is able to support more features of version 6 of the ECMA-262 specification than Node.js can. ECMA-262, or ECMAScript, is the international standard upon which JavaScript is based, and the next version is due to be released in mid-2015.

A particular area of focus for the ECMAScript 6 effort is retooling the language's syntax to make it easier to build and maintain complex applications, something that should appeal to Node.js/io.js developers.

Among the ECMAScript 6 features supported in io.js out of the box are block scoping, collections, generators, promises, and new String methods, and still others are available if you run io.js using the "es_staging" runtime option.

None of this is to say that io.js is looking to "outdo" Node.js, however, or even that it's explicitly trying to compete with the Joyent-backed project. In a blog post from December, io.js contributor Isaac Z. Schlueter said that he could even see the io.js and Node.js efforts re-merging once a few remaining issues are sorted out.

"The work being done in the Joyent Node Advisory Board appears to be heading towards shared goals for the good of the Node community. I expect that this will continue," Schlueter wrote. "The Node community as whole is endeavoring to make a change. The transformation is in progress and we expect to come out better for it."

For now, however, the code for io.js 1.0.1 can be downloaded from the project's GitHub repository. ®

Similar topics

Broader topics

Other stories you might like

  • Red Hat Kubernetes security report finds people are the problem
    Puny human brains baffled by K8s complexity, leading to blunder fears

    Kubernetes, despite being widely regarded as an important technology by IT leaders, continues to pose problems for those deploying it. And the problem, apparently, is us.

    The open source container orchestration software, being used or evaluated by 96 per cent of organizations surveyed [PDF] last year by the Cloud Native Computing Foundation, has a reputation for complexity.

    Witness the sarcasm: "Kubernetes is so easy to use that a company devoted solely to troubleshooting issues with it has raised $67 million," quipped Corey Quinn, chief cloud economist at IT consultancy The Duckbill Group, in a Twitter post on Monday referencing investment in a startup called Komodor. And the consequences of the software's complication can be seen in the difficulties reported by those using it.

    Continue reading
  • Infosys skips government meeting – and collecting government taxes
    Tax portal wobbles, again

    Services giant Infosys has had a difficult week, with one of its flagship projects wobbling and India's government continuing to pressure it over labor practices.

    The wobbly projext is India's portal for filing Goods and Services Tax returns. According to India's Central Board of Indirect Taxes and Customs (CBIC), the IT services giant reported a "technical glitch" that meant auto-populated forms weren't ready for taxpayers. The company was directed to fix it and CBIC was faced with extending due dates for tax payments.

    Continue reading
  • Google keeps legacy G Suite alive and free for personal use

    Google has quietly dropped its demand that users of its free G Suite legacy edition cough up to continue enjoying custom email domains and cloudy productivity tools.

    This story starts in 2006 with the launch of “Google Apps for Your Domain”, a bundle of services that included email, a calendar, Google Talk, and a website building tool. Beta users were offered the service at no cost, complete with the ability to use a custom domain if users let Google handle their MX record.

    The service evolved over the years and added more services, and in 2020 Google rebranded its online productivity offering as “Workspace”. Beta users got most of the updated offerings at no cost.

    Continue reading

Biting the hand that feeds IT © 1998–2022