Good news! For us the migration be a one line code change! Will be interesting to compare the performance between generators and callbacks.
Bruno On Thursday, March 28, 2013 8:17:30 PM UTC+1, cpprototypes wrote: > > Source: http://code.google.com/p/v8/issues/detail?id=2355 > > I think generators have the potential to greatly change how node.js code > is written (for example it could look like this http://taskjs.org). > However, it depends on many factors: > > 1) How easy will it be to migrate existing node.js code? It seems that > most of the community has decided that a simple async library ( > https://github.com/caolan/async) is good enough instead of promises. So > it may be difficult to migrate that to something like tasks.js or anything > else using generators. > > 2) Since node.js developers are used to chaining callbacks and using async > library, there may be a lot of inertia to overcome before generators can > have much impact. > > 3) What kind of impact, if any, will generators have on the core node.js > API? > > > -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
