On Sunday, April 8, 2012 6:21:23 PM UTC-4, Bert Belder wrote: I just tried it out (on Windows) and it seems to be not so bad: when > the application is idle, node's processor usage is negligible. > > Yep, I was worried about this, but it turned out to be good enough for most things I've tried -- see e.g. the demos/ in Node-Five (http://github.com/arturadib/node-five).
I do think we're going to run into performance issues with more demanding applications, like real-time video decoding for example. At that point -- and if necessary -- perhaps we could join the event loop via nextTick()? (Qt only has two entry points for its event loop API -- QApplication.processEvents() which is non-blocking, and QApplication.exec() which is blocking). Thanks for the feedback, Bert! -- Artur Adib Mozilla Labs http://twitter.com/arturadib -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
