A Merger of Front-End JavaScript and Back-End Node.js Foundations

Banner_jsNodemerge.jpg

The most popular and powerful programming language for web development, JavaScript, has been expanding its role from frontend to backend since the introduction of the Node.js.  The JavaScript ecosystem was only supporting the function of presentation layer on the browser initially, but now it continues to support different environments, which includes server, embedded devices, IoT, native apps, DevOps, and protocols.  There are 28 independent JS Foundations such as JS, ESLint, Node.js, jQuery, and Appium, and they all responsible for their individual development and goals.  These organizations may consider joining forces one day, but currently, it’s just the Node.js Foundation and JS Foundation announced an intent to merge. 

“The Node.js Foundation and JS Foundation boards have met several times already to discuss a potential alignment of the communities. The Foundation leaders and key technical stakeholders believe that a tighter alignment of communities will expand the scope of the current Foundations and enable greater support for Node.js and a broader range of JavaScript projects,” said Mike Dolan, Vice President of Strategic Programs, the Linux Foundation. “After having two separate Foundations for two years, we believe there needs to be tighter integration between both Foundations to enable greater support for Node.js and a broader range of JavaScript projects. We look forward to continuing to support the healthy growth of the JavaScript ecosystem and look forward to the potential of supporting an even wider range of projects that the JavaScript ecosystem is dependent on as well as projects that focus on new areas of growth for JavaScript,” the Node.js and JS Foundations’ Board of Directors wrote in a post.

The merger is good news for JavaScript communities of all projects.  For a long time, developers have been working with different JavaScript libraries, and sometimes, there are coherent issues such as the needs of context switching and inconsistent features and functions from the mix of library usages.  There is a need to streamline the process from enhancing the existing codebase, improve collaboration, and engagement among communities. 

Here are the envisioned goals when Node.js Foundation and JS Foundation merger:

  • Enhanced operational excellence;

  • Streamlined member engagement;

  • Increased collaboration across the JavaScript ecosystem and affiliated standards bodies;

  • An “umbrella” project structure that brings stronger collaboration across all JavaScript projects; and

  • A single, clear home available for any project in the JavaScript ecosystem.

As the foundations integrate tighter in collaboration, we will surely see the JavaScript communities thrive and leap in the near future.We cannot wait for the fruitful result of this merger and hopefully, other foundations may consider joining the effort.