11–20 of 33 posts
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?
Andy Wingo mentioned via twitter that he's working on it: https://twitter.com/andywingo/status/316644148532891648
This article in question was already discussed in some depth on HN[2].
Can't wait for an era of much more elegant async code!
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.
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.
Earlier quoted context omitted.
Why didn't ecma just use Mozilla's implementation?
The spec is quite closely modelled after Mozilla's implementation, yes. Other engines just neglected to implement it.
Why would they have? Seems like waiting for ecma approval and specification makes sense.
Earlier quoted context omitted.
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…
[deleted]
Note the opportunity here: all your promises code immediately turns into this: http://taskjs.org/
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.