News for hackers. Stuff that matters.
Re:Object.observe withdrawn from TC39 by dccoolgai on Monday November 02, 2015 @03:24PM (#10494912)
I hope they keep it in V8, if only for debugging. There are some cases where this is the only practical way to see what is mucking with your object and when. If they take it out of the spec, it would be nice if they could add it as a method to console or something, at least.
Re:Object.observe withdrawn from TC39 by lemevi on Monday November 02, 2015 @04:07PM (#10495247)
Re:Object.observe withdrawn from TC39 by AnkhMorporkian on Monday November 02, 2015 @08:45PM (#10496811)
Proxies are brilliant. I used one to create an promise based RPC system that allows you to call any method you want.

So before proxies, we used to do it as:

    await server.rpc.run("methodName", [argumentOne, argumentTwo])
Now, we just do:

    await server.rpc.methodName(one, two)
The proxy traps that method call and returns a promise that runs that on the server. It's very slick and has made our code a lot more readable.
Re:Object.observe withdrawn from TC39 by bcherny on Monday November 02, 2015 @04:14PM (#10495303)
maybe chrome will support this soon...
Re:Object.observe withdrawn from TC39 by randomfool on Monday November 02, 2015 @03:48PM (#10495105)
Isn't it an async callback though?

IMHO, it would be much more useful if it were synchronous.

Re:Object.observe withdrawn from TC39 by stymaar on Monday November 02, 2015 @03:59PM (#10495186)
For debugging purpose, that's exactly what Object.watch does (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...) but this is only a SpideyMonkey feature.
Re:Object.observe withdrawn from TC39 by dccoolgai on Monday November 02, 2015 @03:57PM (#10495173)
It is, but in Chrome devtools it shows you the source of the callback in the stack trace.