days
1
0
hours
0
8
minutes
4
1
seconds
2
0
Free forks

Node.js fork JXcore becomes open source

Natali Vlatko
Direction image via Shutterstock

Delivering on their promise, the team behind Node.js fork JXcore have released the framework as entirely open source, with the SpiderMonkey crew acknowledged for their efforts. The Node.js community can add another notch to is widening belt.

The JXcore crew have taken the project out into open source territory, and they want everyone to know about it. While they’re a fork of Node.js, they also consider themselves as contributing to the community with the intent of keeping the core features of JXcore compatible with Node.

JXcore aims to extend Node’s capabilities to other platforms, and is a framework for developing applications for mobile and embedded devices using JavaScript, leveraging the Node ecosystem. In addition, future editions of JXcore will aim to include JavaScript engines to make Node useful in mobile contexts.

Significance at maximum level

The significance of the project now being open source means more community contribution and engagement. Oguz Bastemar, CTO for Nubisa (the company behind JXcore) stated that the team found it important to open source JXcore prior to final stability updates, as they didn’t want to make future decisions alone.

Team size and resources have also been attributed to the open sourcing decision, with Bastemar confident that JXcore can become a community driven open-source and open-governance project that can realise its full potential.

Ugur Kadakal, CEO of Nubisa, was excited before the release, saying that the added iOS support was a big deal for the team at this stage, allowing developers to build Node applications that run on mobile devices. To achieve this, Bastemar goes on to say that they altered the entire core to include multiple JavaScript engine support:

JXcore has an extensive macro library in order to interact with the underlying JavaScript engines. Our goal is to keep the core features separate from the actual JavaScript engine and it’s API. To reach this goal, we also implemented a wrapper around JavaScript engines.

SpiderMonkey have been acknowledged for their support and efforts in achieving the multi-engine architecture JXcore now boasts, with Bastemar citing SpiderMonkey as the eventual preference for non-IoT plaftorms.

The JXcore team are also reportedly working on implementing a lighter JavaScript engine for IoT devices, and their own JavaScript engine, powered by an LLVM frontend. Contributors planning to develop this kind of system have been urged to contact the team.

For further feature information, details about contributing and FAQ’s, a central hub for JXcore had been set up here.

Author
Natali Vlatko
An Australian who calls Berlin home, via a two year love affair with Singapore. Natali was an Editorial Assistant for JAXenter.com (S&S Media Group).

Comments
comments powered by Disqus