Don't get me wrong, we at BrowserMedia love Rails. Ruby as it's primary language provides enormous strengths for unified development efforts. There is one downside however, Ruby On Rails runs using blocking socket connections. Meaning, function calls and database queries must return before the next gets executed. What this does is, increases the level of threads required to complete a single request. This method consumes massive amounts of resources and causes unnecessary latencies in the receiving of HTTP data.

Enter node.js. A non-blocking framework built on top of Google's V8™ engine. A powerful substitute for a server-side language for those who love Javascript.

Now, this is not like the old school M$ JScript engine and does provide DOM support like Jaxer. It is, as wikipedia states, an event driven I/O framework. You can easily create and deploy a node.js server in minutes.

My background is mainly with frontend development. I have been using Javascript for 15 years and I can appreciate this effort more than most. Being able to use my knowledge of Javascript and applying it on the backend is a win-win for me. I also work with PHP and Ruby but this initiative opens doors for my personal growth.

node.js is still in it's infancy but I am currently learning the ropes and looking to contribute to the project in some fashion. Maybe provide a version of BrowserCMS node.js style. We shall see...