This is my first post here, after years of lurking.

I'm the primary author of https://github.com/facebook/regenerator, a
transpiler for ES6 generator functions that was announced on Hacker News
about two weeks ago: https://news.ycombinator.com/item?id=6594207. On the
linked announcement page, there's a live editor that you can use to
experiment with the transformer (and easily report bugs if you find any).

I've been really encouraged by the uptake (328 stars on GitHub, 21 forks, 9
contributors so far) as well as projects that have begun to use it, such as
Alberto Miorin's browserify transform
https://npmjs.org/package/regeneratorify and Nathan Rajlich's wrapper
command http://npmjs.org/package/gnode.

I have two pretty open-ended questions for this group:

   - Given that this tool will become obsolete as more and more engines
   implement ES6 generator functions, how can we maximize its value in the
   meantime? Are there grey areas in the draft spec that can be illuminated?
   Should I spend my time implementing (or getting others to implement)
   await syntax and/or control-flow libraries that leverage generator
   syntax?
   - How would you design a system that selectively delivers transpiled
   code to ES5-capable browsers and native generator code to ES6-capable
   browsers, so that end users will benefit immediately when they upgrade to a
   browser with native support for generators?

Looking forward to any guidance or feedback you feel inspired to share.

Ben

His errors are volitional and are the portals of discovery.
-- James Joyce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20131103/10d24e64/attachment.html>

This is my first post here, after years of lurking.

I'm the primary author of https://github.com/facebook/regenerator, a
transpiler for ES6 generator functions that was announced on Hacker News
about two weeks ago: https://news.ycombinator.com/item?id=6594207. On the
linked announcement page, there's a live editor that you can use to
experiment with the transformer (and easily report bugs if you find any).

I've been really encouraged by the uptake (328 stars on GitHub, 21 forks, 9
contributors so far) as well as projects that have begun to use it, such as
Alberto Miorin's browserify transform
https://npmjs.org/package/regeneratorify and Nathan Rajlich's wrapper
command http://npmjs.org/package/gnode.

I have two pretty open-ended questions for this group:

   - Given that this tool will become obsolete as more and more engines
   implement ES6 generator functions, how can we maximize its value in the
   meantime? Are there grey areas in the draft spec that can be illuminated?
   Should I spend my time implementing (or getting others to implement)
   await syntax and/or control-flow libraries that leverage generator
   syntax?
   - How would you design a system that selectively delivers transpiled
   code to ES5-capable browsers and native generator code to ES6-capable
   browsers, so that end users will benefit immediately when they upgrade to a
   browser with native support for generators?

Looking forward to any guidance or feedback you feel inspired to share.