One can use non-blocking IO in many languages, on many platforms. Node simply forces people to do so. Essentially forcing lazy/sloppy developers to be better developers. Non-blocking IO is in no way unique to Node however.
∞ Andy Badera
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me:
http://www.google.com/search?q=andrew%20badera
On Wed, Oct 10, 2012 at 1:50 PM, rburton
<[address removed]> wrote:
Sure there is and if you want something that has better language interoperability, look at my buddies project vert.x (http://vertx.io/)
There's a lot of idle time between such operations as I/O operations, database requests etc. Non-blocking I/O is powerful.
On Wed, Oct 10, 2012 at 12:31 PM, Kervin Pierre
<[address removed]> wrote:
>
> Jonathan, what's the primary reason for using Node.js?
>
There's never a good reason to use Node.js
--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
Set my mailing list to email me
As they are sent
Don't send me mailing list messages
http://www.meetup.com/ny-tech/list_prefs/?pref=0
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]
--
-Richard L. Burton III
--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by rburton ([address removed]) from NY Tech Meetup.
To learn more about rburton, visit his/her member profile