thank you for your thoughts, may be there are scenarios where evented frameworks shine, but nodejs is a web framework, so in this scenario the main advantage is that requests don't block each other, so my question is regarding only this scenario: what advantage of using nodejs over gevent monkey patching for building websites? any examples?
On Fri, Jan 4, 2013 at 7:01 PM, Niphlod <[email protected]> wrote: > because for really exploiting evented frameworks you need to code > "evented-ly" also your app. > > Programming languages (also big frameworks like e.g. twisted) that "by > default" have strong support for actors, events, light threads, and so on > (and also for that reason, generally harder to grasp-create-maintain-adopt) > are a level up if confronted with "python+gevent monkeypatching", because > all code in apps and modules and libraries is tailored to that kind of > programming style (and requirements). > > Having wsgi frameworks that run "in the evented way" is the first step - > really nice one, but still one - down to the rabbit hole.....they solve the > issue and the shortcomings of "communicating with the outside", but your > code needs to be refactored if you want to step up a level. > > > Il giorno venerdì 4 gennaio 2013 17:38:55 UTC+1, Vasile Ermicioi ha > scritto: > >> a while ago I saw vert.x (it is on top of jvm) , now that, >> and a question raised in my mind: >> why do I need nodejs or evented frameworks, if importing gevent and >> monkey patching makes everything non blocking? >> >> celery and other goods are already in web2py frameworks, >> so what are your thoughts? >> >> > -- > > > > --
