#node.js

Each Monday we take a step back and analyze what has happened in the previous week. Last week we met two high-profile Java EE Guardians, we witnessed the marriage between Kotlin and Gradle and we learned why the Bitcoin price continues to fluctuate.

Some people still see Node.js as a rookie, but this platform has managed to sneak into the code stacks of tech giants and Fortune 500 companies. It’s safe to say that Node.js is playing in the big leagues thanks to giants such as Microsoft, LinkedIn, Netflix, PayPal and a plethora of others.

Choosing the right framework for a project is still considered to be the most daunting task by business and site owners looking to strengthen their web presence. No worries, we have compiled a list of frameworks associated with Node.

There are many reasons why developers (regardless of experience level) should use Node.js for web application development, starting with its speed and ending with its proficiency at multi-user, real-time web applications. Not to mention that three years ago Nodejitsu reached out to the npm community for help running the public npm servers and raised over $300,000 for the project, proving that the community is both active and generous.

If you can keep up with a fast-paced upgrade schedule and want access to new features sooner, then the release of Node.js 5.0 is right up your alley. The team behind the JavaScript-based runtime environment have now unveiled two release lines.

The new Node.js 4.2 release has been christened “Argon”, the first drop under the new Long Term Support plan that provides various levels of support over a 30 month period. The plan aims to help operations teams and enterprise application development.

Three months after the Node.js Foundation started work on a new release candidate, Node.js 4.0.0 has been released – now featuring the io.js fork code base for the very first time.

Expected to be the last series under their forked banner, io.js has progressed to version 3.0.0. Breaking changes show up in the form of V8 upgrades, along with preparations around the native side of the platform for the upcoming Node.js merger.

After initially breaking away from the grips of Joyent and Node.js, io.js has now officially signed up with the Node.js Foundation, putting an end to the community split.

A new drop from io.js brings in the upcoming version of JavaScript (ES6), with io.js 2.0 delivering a bevy of bug fixes and features no longer behind a staging feature flag.

Persistence has payed off in the latest Node.js development, with staff from io.js and the Linux Foundation working to bring the band back together. The spin-off framework might finally be coming home.

Nowadays, everybody’s talking about continuous delivery, but how many of us can say we’ve encountered “Local Continuous Delivery”? In this guest post, blogger Chris Yanx shows us a novel approach to automating a local build system with Grunt, Node.js and Java.

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.

Following the release of Node.js 0.12, Joyent has announced a Node.js foundation led by major industry players. But will it help patch up the schismatic Node community?