In part 1 of my blog post I’ve reviewed the state of Node.js and the importance of the human aspect of open source development.
Node by Another Name
In 2015, the so-called community “side-project”, io.js, quickly grew in features and contributors, proving that an openly governed open source project could deliver reliable and cutting edge server software that can be used in production. Node.js’ corporate sponsor agreed to relinquish absolute control of the project, so that the newly founded non-profit Node Foundation could take control of the project. The foundation was founded on the principals of open governance; with tech giants and members of the community getting equal voice in the direction and future of Node.js. In the fall of 2015 the community merged io.js with Node.js. Shortly after the first long-term supported (LTS) version of Node.js was released as version 4.
Node v4 supports language features from the recently ratified ES 2015 standard. It’ll be supported with critical bug and security fixes until 2018, a whopping 30 months after its release. Best of all, work on future versions of Node is already underway with Node v5 with new LTS versions planned to be released on a yearly cadence. This predictable schedule is essential in bringing 3rd party tools and libraries on the same beat as the core framework making it possible to have high quality releases of new versions of development tools and frameworks on day one.
In 2015, the community succeeded in bringing the corporate and hacker communities together and managed to release a truly ground breaking product demonstrating how open governance can transform software development in the coming years.
Furthermore, Node.js has great support from the wider community in the form of thousands of Node Package Manager (npm) packages. Npm makes it more convenient, dependable and easier than ever to share and reuse functional slices of code while having full access to the source code. Open source is an undeniable part of professional development. Npm makes it possible to utilize open source code safely, but more importantly it makes contributing back to the open-source community with your own npm packages very easy.