On Sun, Jan 2, 2011 at 3:27 AM, jemptymethod <[email protected]> wrote: > I don't get some of the fuss over node.js. Sure, it can be great to > write most of your code, both client and server side in one language. > > But what's all the fuss over the event loop. Like they invented it or > something? It's been part and parcel of other frameworks, and even > the Tcl language, for over two decades.
https://docs.google.com/present/view?id=dzg6rkg_75g3j8qg8n I gave a presentation on it not to long ago. Yes, the idea isn't "new", but the speed of JS engines coupled with the fact that JS has no notion of I/O has put it in a powerful spot, that Node really has taken exploited. Also, JS was built for the event loop, in my experience, many of the languages have added to concept of event loop to an already blocking system (e.g. Python and Twisted, and Ruby and EventMachine). I am not familiar with the other languages you mentioned. The intention of Node wasn't to build a system that could run code both client and server same stack (although that has turned out to be a plus). It was focused on nonblocking I/O and event driven servers and performance. Hope that helps. If you want to dive further, search the the NodeJS Mailing List or pop this question over there. -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
