A small correction - Object.observe is not a shipping feature at the moment. It may exist in Chrome 34 beta, but Chrome 33, which is the current stable release, does not have it.
By the way, it would be nice to have all of the Chromium related (Blink, V8, WebRTC and anything else that is built into Chromium) intent threads in one place, instead of subscribing to many groups that publish intent threads. I guess this has caused Object.observe to be excluded from the latest Chromium blog post about Chrome 34<http://blog.chromium.org/2014/02/chrome-34-responsive-images-and_9316.html> . For references, here is the missing intent thread for Object.observe - https://groups.google.com/forum/#!searchin/v8-users/subject$3Aintent|sort:date/v8-users/aeSFJK1L5n4/zvC0E-2cXWUJ And other V8 intent threads (mostly intents to implement. ArrayBuffer.isView, Object.observe and this thread are the only intents to ship) - https://groups.google.com/forum/#!searchin/v8-users/subject$3Aintent%7Csort:date ☆*PhistucK* On Thu, Mar 20, 2014 at 11:46 AM, Jochen Eisinger <[email protected]>wrote: > FYI - V8 promises will be enabled hopefully for M35. The v8 implementation > was updated to reflect the Jan 30 changes. > > best > -jochen > > ---------- Forwarded message ---------- > From: Andreas Rossberg <[email protected]> > Date: Mon, Mar 17, 2014 at 4:47 PM > Subject: [v8-users] Intent to ship ES6 promises & weak collections > To: "[email protected]" <[email protected]> > > > We intend to soon ship both ES6 promises and weak collections > unflagged in V8. Since the former depends on the latter, I'm combining > both in this mail. > > > PROMISES > > Promises have been accepted into ES6, and have hit the draft spec > earlier this year [1]. They are already used in DOM APIs. Mozilla also > plans to ship promises in FF25. The current implementation of promises > in Chrome lives in Blink, a V8-side implementation has been done last > fall. > > We intend to ship Chrome 35 with the V8 implementation replacing the > Blink one, since it is more up-to-date wrt the latest spec changes, > and (we believe) more efficient. That means that V8 will turn on > promises by default (they are currently being moved to es-staging). > > Owners: [email protected], [email protected] > > [1] > http://people.mozilla.org/~jorendorff/es6-draft.html#sec-promise-objects > > > WEAK COLLECTIONS > > Weak maps and sets have been in the ES6 draft for a long time [2, 3], > and our implementation has been stable for years. Moreover, it is > (under internal APIs) already used in shipping features, such as > Object.observe. > > Our self-hosted implementation of promises uses ES6 weak maps > internally. Due to this dependency, we are moving both features to > staging simultaneously, and intend to ship them together. > > Owner: [email protected] > > [2] > http://people.mozilla.org/~jorendorff/es6-draft.html#sec-weakmap-objects > [3] > http://people.mozilla.org/~jorendorff/es6-draft.html#sec-weakset-objects > > -- > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > --- > You received this message because you are subscribed to the Google Groups > "v8-users" 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/d/optout. > > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" 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/d/optout.
