Object.observe

[jpillora]

Couldn't find an issue about this, but if one does, please link and I'll close :)

I see there's an ObjectObserve branch but it hasn't been touched in a year. And this post by Misko. I can't find Object.observe in the Angular source, though it could be hiding...

Chrome has had Object.observe since version 25 (http://www.chromestatus.com/features/6147094632988672). Are there plans to drop it in and use it when available?

Edit: It's been in Chrome for a long time, though as @bobslaede points out, it's still under the "Enable Experimental JavaScript" flag.

Demo: http://jsfiddle.net/jpillora/wvA64/

[bobslaede]

I'm not sure it's not only in Canary, and it is still behind a flag I think.

[jpillora]

Run the demo I've linked. I'm on Chrome Version 28.0.1500.95 Stable and it runs. According to the chromestatus page (also linked), it's been in stable since Version 25

[jpillora]

Damn! Just checked, I've got "Enable Experimental JavaScript" flag on. My mistake :(

[bobslaede]

I just did in Chrome 28.0.1500.95 on windows. It didn't run.

[bobslaede]

:)

[IgorMinar]

we are working on O.o() but as you observed it's going to be a while before O.o() is wildly available in production.

we don't have enough of O.o() integration ready to share it as a branch, but stay tuned. @jankuca and @btford are on it.

[piether]

What's the status on this? Object.observe is supported by Chrome 36. http://www.chromestatus.com/features/6147094632988672

[caitp]

O.o is being worked on by @EisenbergEffect for https://github.com/angular/watchtower.js at the moment, and will be used in v2.0.0

However it's unlikely that we can leverage it in 1.x. It may be feasible, but it's not something that will necessarily make it into 1.x without significant refactoring to the current dirtychecking algorithm

[btford]

I'm going to close this issue because it's not particularly actionable, but thanks everyone for your interest! As @caitp mentioned, you can track the progress of our new change detection library in the watchtower.js repo.

[kevin-smets]

Just inquiring, leveraging O.o() in 1.x will never be done? The performance on a low end Android is unbearable once you hit like 400 watchers (Samsung Galaxy Tab). I am not using the built in WebView but include a Chromium engine (v36) in my apk so it supports O.o().

This would sure make a big difference so that's why I'm just wondering if it ever will be an option, I'm not getting my hopes up, but still, can't hurt to check, no? Thanks!

[DexterMorg4n]

Very interested in the O.o(). Is it already included in the latest AngularJS or do we have to write it ourselves ? Today HTML5 is turned into a standard so we can safely say the O.O() will be widely adopted, if it isn't already everywhere.

Just wanted to know if I start writing or not. For larger sets $watch does create problems.

[caitp]

Very interested in the O.o(). Is it already included in the latest AngularJS or do we have to write it ourselves ? Today HTML5 is turned into a standard so we can safely say the O.O() will be widely adopted, if it isn't already everywhere.

Just wanted to know if I start writing or not. For larger sets $watch does create problems.

V8 is the only engine which implements O.o, and it's ridiculously slow in comparison to dirtychecking in angular.

It will not be included in 1.x, and is not likely to be included in 2.x if it doesn't get picked up by additional browsers, and doesn't improve in speed.

[DexterMorg4n]

Hmm.. Thanks. How come all benchmarks (at least everything I could find) shows O.o() as being a lot faster ? Example :: http://www.html5rocks.com/en/tutorials/es7/observe/

[caitp]

You mean from this quote?

For example, last year Angular found that in a benchmark where changes were being made to a model, dirty-checking took 40ms per update and O.o() took 1-2ms per update (an improvement of 20-40x faster).

Performance of O.o is still being worked on in v8, and may improve over the course of the near future. But unfortunately, as-is, it prevents some optimizations, and requires a lot of special casing in various algorithms which include hacks --- and the whole recording and queueing of changes is not cheap, unfortunately.

We will hopefully see performance improve, but for the time being it's not really there. And even if it were there, v8 is only one piece of the market.