Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

V8 developers start working on ES6 generators for JavaScript

code.google.com

Post reply on HN
Print view View original

21–30 of 33 posts

Re: V8 developers start working on ES6 generators for JavaScript

#21

Post by evilpie »

apaprocki wrote: post #15
Mahn wrote: post #6

A bit offtopic, but: are all chromium & V8 team members Googlers? just wondering, chromium and V8 are both open source, but I've never head of any major contributors other than Google itself.

Anyone can contribute to V8. I've had a patch accepted and we are paying Igalia to add the ES6 generator support. The water's fine, jump in!

Just to hop on the train. This is true for SpiderMonkey as well. Just come visit us on IRC: irc://irc.mozilla.org/#jsapi. We are active around the clock, sometimes even at weekends. We discuss a lot of stuff directly on IRC, so you feel really involved. See also: https://wiki.mozilla.org/JavaScript:New_to_SpiderMonkey

Re: V8 developers start working on ES6 generators for JavaScript

#22

Post by mraleph »

evilpie wrote: post #8
Mahn wrote: post #6

A bit offtopic, but: are all chromium & V8 team members Googlers? just wondering, chromium and V8 are both open source, but I've never head of any major contributors other than Google itself.

From what I gathered (ie. talking to mraleph) v8 is mostly just Google employees. I can't speak about Chromium. The contributor situation is not vastly different for SpiderMonkey or JSC. I am usually the only contributor, besides 1-3 others that sometimes work on SpiderMonkey. Edit: I think some ports are maintained from people outside Google. It's not really easy to tell, because most people have @chromium addresses…

MIPS port is fully maintained by MIPS people. These days they even have commit rights.

You can see full list of people and organizations that contributed to V8 in the AUTHORS file.

Re: V8 developers start working on ES6 generators for JavaScript

#24

Post by cpprototypes »

recuter wrote: post #19
jlongster wrote: post #2

Note the opportunity here: all your promises code immediately turns into this: http://taskjs.org/

JS next seems almost as if they turned Javascript into Python. I am pleased.

I wish V8 already had generators back when node.js started. It would've been a true solution to callback hell. There's libraries like async to help with that, but it's not as good as something like tasks.js could be.

Re: V8 developers start working on ES6 generators for JavaScript

#26

Post by recuter »

cpprototypes wrote: post #24
recuter wrote: post #19

Earlier quoted context omitted.

JS next seems almost as if they turned Javascript into Python. I am pleased.

I wish V8 already had generators back when node.js started. It would've been a true solution to callback hell. There's libraries like async to help with that, but it's not as good as something like tasks.js could be.

But on the other hand Twisted is not a panacea either, not that this is a perfect parallel or anything. But I agree, this is definitely a step in the right direction.

I wonder if it will be feasible to code in JS Next and have a compiler step somehow take care of backporting. Probably not.

Re: V8 developers start working on ES6 generators for JavaScript

#27

Post by _alex4nder »

olegp wrote: post #5

In the mean time you can use fibers with Node. I've been using them for StartHQ ( http://starthq.com ) via Common Node ( https://github.com/olegp/common-node ) and to be honest I don't see how I could have made it maintainable with promises, let alone no flow control library at all.

Agreed. Fibers are a great way to take simple synchronous-looking code and make it play well with the rest of node, without resorting to threads.

Re: V8 developers start working on ES6 generators for JavaScript

#28

Post by coldtea »

recuter wrote: post #19
jlongster wrote: post #2

Note the opportunity here: all your promises code immediately turns into this: http://taskjs.org/

JS next seems almost as if they turned Javascript into Python. I am pleased.

I am pleased too, but unfortunately it seems like they turned it into Python 3.

That is: not a stable, cross platform, version on the horizon yet --not even excluding IE--, and we're in for a long wait.

Re: V8 developers start working on ES6 generators for JavaScript

#29

Post by coldtea »

firefoxman1 wrote: post #9
Yoric wrote: post #7

Ahaha, finally! I have been waiting to use this feature on the web, well, since Mozilla implemented it, which must have been at least 5 years ago.

Why didn't ecma just use Mozilla's implementation?

Because the ES6 ECMA is made by a bloody time-wasting committee and the V8 team is also slow as hell to implement JS-level stuff (and let's not speak of IE and MS).

Re: V8 developers start working on ES6 generators for JavaScript

#30

Post by samth »

firefoxman1 wrote: post #9
Yoric wrote: post #7

Ahaha, finally! I have been waiting to use this feature on the web, well, since Mozilla implemented it, which must have been at least 5 years ago.

Why didn't ecma just use Mozilla's implementation?

Ecma is a standards body, not an implementor. And standardizing things doesn't make them appear in other engines.
Post reply on HN