Node.js has generally caused two reactions in people I've introduced it to. Basically people either "got it" right away, or they ended up being very confused. If you have been in the second group so far, here is my attempt to explain node: It is a command line tool. You download a tarball, compile and install the source.It let's you run JavaScript programs by typing 'node my_app.js' in your terminal.The JS is executed by the V8 javascript engine (the thing that makes Google Chrome so fast).Node provides a JavaScript API to access the network and file system Understanding node.js » Debuggable Ltd Understanding node.js » Debuggable Ltd
Node.js Step by Step: Blogging Application Node.js Step by Step: Blogging Application In the previous episode in this session, you were introduced to Node.js by creating a simple web server that displayed the obligatory "Hello world" text. Today, we'll take our knowledge to the next level as we begin the implementation of our blog engine application. During the course of this, episode we'll be adding our very first route and view. To do this, we'll learn a little more about Node's predilection for asynchronous behavior, and we'll also take a look at the File System ('fs') module for reading our first view into our application. By the end of this portion of our series, you'll have a little better understanding of Node and of one of its libraries that makes it possible to use Node for scripting.
Node.js From the Enterprise Java Perspective | Shine Technologies Blog Node.js From the Enterprise Java Perspective | Shine Technologies Blog Node.js currently is getting much attention because it uses a concurrency model that shows great promise in scalability: event-driven asynchronous Input/Output. This model can handle thousands of concurrent user-requests and do that with a tiny memory footprint, things that cannot be done with the traditional multi-threaded concurrency model of Enterprise Java. This article explains this new approach from the viewpoint of an Enterprise Java developer.
On TermKit | Steven Wittens - Acko.net I've been administering Unix machines for many years now, and frankly, it kinda sucks. It makes me wonder, when sitting in front of a crisp, 2.3 million pixel display (i.e. a laptop) why I'm telling those pixels to draw me a computer terminal from the 80s. And yet, that's what us tech nerds do every day. The default Unix toolchain, marked in time by the 1970 epoch, operates in a world where data is either binary or text, and text is displayed in monospace chunks. On TermKit | Steven Wittens - Acko.net
Web console with node.js « Gonzalo Ayuso | Web Architect var timeout = 5000; var wsServer = '127.0.0.1:8880'; var ws; function cleanString(string) { function pad(n) { return ("0" + n).slice(-2); Web console with node.js « Gonzalo Ayuso | Web Architect
Node.js Tutorial Roundup | blogfreakz.com Javascript has always been important but usually it just hangs around in your browser, getting stuff done. The buzz on the internet is node.js, an event based, server side javascript based on Google’s super-fast V8 engine. It allows you to make high performance, large scale applications. Node.js Tutorial Roundup | blogfreakz.com
Learning Node.js « JTeam Blog / JTeam: Enterprise Java, Open Source, software solutions, Amsterdam For projects and for some experiments I want to get a better way to do server push. With the new HTML 5 becoming the standard and therefore WebSockets becoming available in all mayor browsers, it seems that WebSockets is the way forward. A very nice implementation of WebSockets that is backwards compatible with older browsers is available through Socket.io. This is a Node.js library. Learning Node.js « JTeam Blog / JTeam: Enterprise Java, Open Source, software solutions, Amsterdam
NodeJS is pretty popular these days, so I took some time to have a in-depth look at it and analyze the pro/cons of using it against another server-side technology. The first issue I can see is not technical : you have to rewrite all your programs and libraries by passing callback methods. This is a bit annoying since if you want to make three async requests you have to write the following : async1(function(result1) { async2(function(result2) { async3(function(result3) { }); }); }) You also have to adopt the same style as soon as you make a regular function call that will itself make an async call. Nicolas Cannasse Blog - Is NodeJS Wrong ? Nicolas Cannasse Blog - Is NodeJS Wrong ?
Codes from the Underground - Endtable, an ORM for CouchDB on Node.JS
Diving into Node.js – Very First App What do I have till now? After Node.js is istalled, described in my previous post, I can simply run this command: stoimenpopov:~# node server.js and this will start the server with the code within server.js. But what’s the code of server.js? Following the instructions of Node’s homepage and most of the tutorials I’ve found, I can simply copy/paste the code from the first lines of Node’s page: Diving into Node.js – Very First App
Diving into Node.js – Introduction & Installation Why I Need Something Like Node.js? First of all the use of some software is needed not because of itself, but because of the need of some specific functionality. In my case this was the need of real time news feed. Of course there is a way to make this without Node.js, as I’ll describe later in this post, but there are several disadvantages. Diving into Node.js – Introduction & Installation
I’d been curious about node.js for a while. Finding Twitter all atwitter about it at any particular moment isn’t difficult. People are experimenting with it and other JavaScript technologies, like WebSockets. Yahoo even showcased a multi-core HTTP server written in it a few months back. I already had a decent working knowledge of JavaScript. Node.js: A Beginner’s Perspective

Learning Javascript with Object Graphs

Static Version One of the secrets to being a super effective JavaScript developer is to truly understand the semantics of the language. This article will explain the basic elemental parts of JavaScript using easy to follow diagrams.
James Carr » Blog Archive » Lessons Learned With My Recent Node.js App Recently I created a little web app for a friend’s conference to accept talk submissions and gather votes on those submissions to rank the top ones. For this task I used heroku’s node.js beta preview to host the application and a free couchone instance for the data store. Things were a bit rocky but I learned some important lessons that I thought I’d share.
JSAN - JooseX.CPS 0.11 JooseX.CPS - Implementation of the Continuation Passing Style 1 for JavaScript, plus some syntax sugar, simplifying its usage in Joose methods and method modifiers Stand-alone usage: The same in OOP:
isaacs's npm at master - GitHub README.md npm(1) -- node package manager This is just enough info to get you up and running. Much more info available via npm help once it's installed. You need node v0.8 or higher to run this program. To install an old and unsupported version of npm that works on node 0.3 and prior, clone the git repo and dig through the old tags and branches.
JSAN - Joose 3.011
Joose - advanced meta-class system for JavaScript
Geddy web framework for Node.js
reid's node-jslint at master - GitHub
Limiting Concurrency in Node.js
Node.js Knockout
Building a Scrabble MMO in 48 hours » Startup Monkeys
Moving the Server to the Browser
Hummingbird - Millisecond Real-time Web Analytics with Node.js