90 days of node.js - Day 1

I've been on and off the node bandwagon more frequently that I would like to admit. Node is pretty amazing in the way it frees the JavaScript browser from the confines of the browser. It helps the programmer use the language outside of browser quirks and into the realm of being able to create an end to end solution.Granted, this isn't new and the JVM has also had the ability to write JavaScript and run it in the JVM. But, that has involved a lot of burnt cycles figuring out the java code, build cycles, maven or any files... you get the drift. The biggest plus of node.js as far as I am concerned as a web developer is the ability to write JavaScript for both the client side and server side ends of the application. One language tying both your access to the datastore and the presentation layer. That is just fantastic.

That is also the reason I have never really gotten into node. By virtue of working on the Java web stack, more often than not I have to use a view layer bundled with one of the frameworks - be it jsps, gsps or the ilk. The backend also tends to be a Java framework which makes life easy. Inserting a node.js backend is not necessarily something that is easy to get away with, especially in enterprise environments.

So, in the spirit of getting myself off my ass which has been the general trend of this year so far, I am trying out different things in the node.js ecosystem for 90 days and document my work. 90 days of node.js. I am not a stickler for guidelines, so this might take more than the promised 90 days, but I will try to stick to the plan and hopefully by Septmber have enough material to push to github. The general plan is sketchy - I want to learn more about bower, express and streams in general, but the particulars are kind of sketchy.

That said, this is the first day of node. And the first step is installing node.That is as simple as clicking on the big, green Install button on the node.js site. I usually work on windows and my current build is win 8.1. All my installs usually go into some sort of sandbox folder - just becos.

Et voila and we're off to the races. Next stop, creating a simple module to stream data from a file.