FAQ
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscribe@googlegroups.com
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 nodejs+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

  • Ben Noordhuis at Mar 28, 2013 at 7:31 pm

    On Thu, Mar 28, 2013 at 8:17 PM, 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?
    We won't be switching over right away, if that is what you mean.
    We'll probably let user modules duke it out first, see what works and
    what doesn't, then steal^Wuse that as a source of inspiration.

    --
    --
    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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Floby at Mar 29, 2013 at 10:40 am
    Generators have some nice applications. Like iterators and such.
    I wrote https://github.com/Floby/node-object-iterator to return a generator
    and it was sometimes a pain to keep states and such.
    On Thursday, 28 March 2013 20:31:20 UTC+1, Ben Noordhuis wrote:
    On Thu, Mar 28, 2013 at 8:17 PM, 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?
    We won't be switching over right away, if that is what you mean.
    We'll probably let user modules duke it out first, see what works and
    what doesn't, then steal^Wuse that as a source of inspiration.
    --
    --
    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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Bruno Jouhier at Mar 29, 2013 at 12:53 pm
    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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Marcel Laverdet at Mar 30, 2013 at 4:22 am
    ?_? node has had generators since early 2011.

    ;) ;) ;)

    On Fri, Mar 29, 2013 at 9:53 PM, Bruno Jouhier wrote:

    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<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 <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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    --
    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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Mark Hahn at Mar 30, 2013 at 6:50 am
    node has had generators since early 2011
    Reference please?

    On Fri, Mar 29, 2013 at 9:22 PM, Marcel Laverdet wrote:

    ?_? node has had generators since early 2011.

    ;) ;) ;)

    On Fri, Mar 29, 2013 at 9:53 PM, Bruno Jouhier wrote:

    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<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 <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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    --
    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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    --
    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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Alex Kocharin at Mar 30, 2013 at 7:59 am
    =A0He was probably talking about node-fibers=A0=A0He was probably talking about
    node-fibers=A0
  • Arunoda Susiripala at Apr 1, 2013 at 1:58 am

    On Saturday, March 30, 2013, Alex Kocharin wrote:
    He was probably talking about node-fibers

    --
    // alex


    30.03.2013, 10:50, "Mark Hahn" <mark@hahnca.com <javascript:_e({},
    'cvml', 'mark@hahnca.com');>>:
    node has had generators since early 2011
    Reference please?


    On Fri, Mar 29, 2013 at 9:22 PM, Marcel Laverdet wrote:

    ?_? node has had generators since early 2011.

    ;) ;) ;)


    On Fri, Mar 29, 2013 at 9:53 PM, Bruno Jouhier wrote:

    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<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 <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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.




    --
    --
    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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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
    --
    Arunoda Susiripala

    @arunoda <http://twitter.com/arunoda>
    <http://gplus.to/arunoda>https://github.com/arunoda
    http://www.linkedin.com/in/arunoda

    --
    --
    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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Marcel Laverdet at Mar 30, 2013 at 9:24 am
    https://github.com/laverdet/node-fibers

    (only slightly trolling)

    On Sat, Mar 30, 2013 at 3:49 PM, Mark Hahn wrote:

    node has had generators since early 2011
    Reference please?

    On Fri, Mar 29, 2013 at 9:22 PM, Marcel Laverdet wrote:

    ?_? node has had generators since early 2011.

    ;) ;) ;)

    On Fri, Mar 29, 2013 at 9:53 PM, Bruno Jouhier wrote:

    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<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 <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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    --
    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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    --
    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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    --
    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 nodejs@googlegroups.com
    To unsubscribe from this group, send email to
    nodejs+unsubscribe@googlegroups.com
    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 nodejs+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupnodejs @
categoriesnodejs
postedMar 28, '13 at 7:17p
activeApr 1, '13 at 1:58a
posts9
users8
websitenodejs.org
irc#node.js

People

Translate

site design / logo © 2022 Grokbase