javascriptCannot understand node.js

From someone with few experience in JS, what do you recommend for learning Node.js?

I read a lot in the forum about event driven, non-blocking , async, callbacks, etc but I don't know what's that!

Where can I learn the basics in order to understand all that terms and in the future, node.js?

Thanks!

The concepts you mention (event-driven, non-blocking, async, callbacks) aren't specific to JavaScript and understanding them in a more general context is valuable. They all revolve around gracefully handling resources over which we have no control.

Imagine waiting for data from a TCP connection, waiting for the OS to delete a file, or waiting for a user to click a button. If you programmed this in a step-by-step fashion (step-by-step is synchronous), you'd cruise along - "do step 1", "do step 2", "do step 3" - until you hit the step "wait for something to happen". At that point, your program would stop and refuse to budge until it received the data, received delete confirmation, or received the button click. In other words, the call blocks the program from proceeding. This is pretty inefficient considering there are likely other TCP connections, file operations, and UI actions that need our attention and don't depend on the item we're waiting for.

In many cases, it would be better to indicate we're interested in a resource and receive notifications outside of step-by-step instructions when the resource changes. From your list of concepts:

  • Events are changes in the resources we're interested in - our TCP connection received some data, the file delete is complete, or a user clicked a button.
  • Asynchronous calls tell the OS or runtime that we're interested in doing something with a resource. They are non-blocking - our program can work on something else while it waits for a change in the resource.
  • Callbacks are functions to be executed when the resource changes. An asynchronous resource call often accepts one or more references to callback functions (one for success, one for an error, etc...). When the resource changes, the runtime calls the appropriate callback.

We can see these concepts illustrated by renaming a file with node.js:

var fs = require('fs');

// args (current file name, new file name, callback function)
fs.rename('/tmp/hello', '/tmp/world', function (err) {
  // this occurs when the rename is complete
  if (err) throw err;
  console.log('rename complete');
});
console.log('step after rename');

The third argument may look strange. It's an unnamed (anonymous) function that will be called when the rename is complete.

Note that since fs.rename is asynchronous, it's impossible to tell if we'll see the 'rename complete' or 'step after rename' message first. That's the downside to event-driven/asynchronous programming - if we have a complex set of interdependent tasks, we need to be extremely careful to insure dependent tasks complete before the tasks that depend on them. The fact that the order of async call completion can change can lead to very subtle bugs.

See also:


Edit per donald's request:

The best way to understand node.js is to download, build, install, and use it. You'll need:

  • Mac OS or Linux. If your comfortable with Cygwin, that may also be an option but if you're running Windows I find it easier to run Linux in a virtual machine.
  • Git - not required but it makes fetching the code repository easy.
  • A way to debug your application. See this question. Initially, writing debug info to the console may work. Eventually, you'll want robust debugging.
  • An idea - what is it you want to do with node.js? If you're interested in an overview of its capabilities, browse its API.

Most tutorials focus on node.js's ability to quickly build an Http server:

Keep in mind that node.js fills a very particular niche - it's designed to build network programs. It may not be the right tool for other types of programs.

The basic concepts you need to understand to make progress with Node.js are the idea of events, event emitters, and event listeners.

In Node, most functions you can call are non-blocking. When you call fs.ReadStream(), for example, it returns a ReadableStream object. That object is an EventEmitter, so in order to do anything with the contents of the stream, you need to attach a listener to the object, which is a function that gets called when a particular event occurs.

So something like this works:

var fs=require('fs');
var stream = fs.createReadStream("/var/log/messages", { 'flags':'r' });
stream.addListener('data', function(someData) {
        console.log(someData);
});

This reads all of the text from the given file, and writes it to the console. When there is data to read from the stream, your function gets called, and is passed the data from the file.

Interestingly, once there is no more data to read from the file, the script exits. Node only stays running as long as there's a valid event listener attached to an emitter, or another asynchronous callback (like a timer) is active.

Javascript: The Good Parts is one of the best books ever for learning the ins and outs of the language and not just DOM stuff http://www.amazon.com/JavaScript-Good-Parts-Douglas-Crockford/dp/0596517742/ref=sr_1_1?ie=UTF8&s=books&qid=1284520954&sr=8-1

Well, this Stackoverflow question has a lot of awnsers in it that will teach you more about learning JS.

http://stackoverflow.com/questions/3696199/how-can-i-truly-master-javascript/3696765#3696765

JavaScript basics are actually the same basics as any other languages (hello world app, etc), the real difference lies in the 'advanced' areas of JavaScript.

Related Articles
  • I am having a hard time understanding how to export a file and then include it elsewhere on node.js. Suppose I am working on a game and I want to have the variables which define an object, or more than one, for example a var enemy: var enemy = { heal
  • I have a question to this part of the Node.js documentation: Modules are cached after the first time they are loaded. This means (among other things) that every call to require('foo') will get exactly the same object returned, if it would resolve to
  • Redis has me very confused. I simply need a set of users. The keys for the users will be their userIDs: var user = userID; I then want hash values set for these users, and right now I only have one - socketID: // add first user redis.sadd("users"
  • I've been searching for the solution to this for days and would love any solutions or recommendations. I am building a very simple blog with node.js, express, and mongo db according to this how to node tutorial. I am doing this as practice in order t
  • If I understand node.js correctly, then a single event handler that does not release the cpu (infinite loop for example) can freeze the whole system. Is this correct?
  • I have not gone through the code detail of node.js . But, going through some research about thread in Node.js, I found that it has single thread for accepting connection from multiple clients. When connected with client it fires connection events and
  • This question is the following of my other question here: http://stackoverflow.com/questions/3707746/cannot-understand-node-js I decided to learn JavaScript, however and in spite of I learn by doing, I don't find anything I can be doing in order to l
  • I'm new to javascript, and jumped right into node.js. I've read a lot of theory, and began well with the practical side (I'm writing an API for a mobile app), but I have one basic problem, which has lead me to middleware. I've successfully implemente
  • I asked a similar question, but before it got closed as a duplicate I forgot to mention I want to understand how to do this without using a third party library. How can I dynamically generate Html content with Node.js? So, how can I programatically g
You Might Also Like