New PluralSight Course: io.js ... (or is it?)

Posted by Marcus Hammarberg on June 5, 2015
Stats

For the last couple of months I have used io.js to run all my Node applications. I’m not going back. The transition has been very smooth, with a few minor things that you need to think about. And as always; I improved my existing skills by just moving outside the comfort zone a little bit.

I thought that my journey could be an interesting PluralSight course. So did they.

I’m happy to release this as my second course on PluralSight, Koa Js being the first.

Here’s the link to the course

A very interesting challenge presented itself at the end of the production as well. Tell you soon.

The course is in three parts (and a summary):

  • What is io.js - in this module I introduce what io.js is (and what’s it’s really called) and how to install it using nvm. Now that’s even simpler with nvm-latest
  • Running Node apps on io.js - this is the meat of the course showing some of the small quirks getting started but mostly showing what possibilities that io.js opens up for your Node applications. Especially around EcmaScript 6. There’s also a section about how make sure that you actually are using the correct version of the framework. I blogged about that before
  • Deploying to Heroku - in this module I show how to convert an existing application and then what you need to think about to make sure that your configuration is correct. This module serves a little bit as repetition of the second part.

The twist

I was done. All the material was handed into PluralSight and I was just waiting for the launch. And then this happened.

io.js decides to join the Node Foundation.

Basically io.js will go away, so will Node and “new node” will replace it. Now this is not as dramatic as it first might sound. io.js was created as a clone of our Node and released in 1.0.0 early this year. Since then active development has taken place in both Node and io.js, but most development has taken place in io.js, of course.

“new node”, that most likely will be called nodejs, will hence be a fork of io.js.

So the threat to the relevance of my course is not that big. In fact it’s an opportunity. It only woke up on the wrong side of bed that morning, so it was a little bit hard to see it as a opportunity at first.

It’s is an opportunity because the things thought in the course will be the foundation for how “new node” will work. Basically - if you know io.js you know “new node”.

The course is published here.

Go watch it now!



Published by Marcus Hammarberg on Last updated