Lingering in stage 0

[SanderElias]

This project seems to linger at stage 0 for over a year now. (at least that is how it looks like from this repo)
How about a status update? I would love to see this progress. preferably into stage 4 and into production!

[domenic]

I guess we should withdraw it. We are not able to overcome the Node.js objections in #9.

[SanderElias]

That's too bad. I quickly glanced over the thread, and this is not light reading.
However, it seems to pivot around require, with the coming import stuff in node v8 things might change. Perhaps a fresh look might bring new insights. When I have an hour to set apart, I will really read the whole thread more thorough. I'm good in asking stupid questions, and sometimes those help to get things along!

[bmeck]

@domenic is it not possible to withdraw the error handling?

[domenic]

I am not really interested in working on or supporting an incomplete proposal that doesn't include error handling.

[bmeck]

Moving to Node CTC nodejs/CTC#166

[enko]

@domenic Is there anything that I can do, to push this proposal forward?

If this proposal would go forward, there would be at least a hint of support for async/await in angular via https://github.com/angular/zone.js/issues/740.

[Jamesernator]

Pending one change (nodejs/node#28317) Zones could actually be entirely writable in Node using the async_hooks API.

It would be nice to consider reviving this with that in mind.

[benjamingr]

@Jamesernator that would not make zones writeable in Node because of error handling. If zones were just async hooks node would not object to them.

Also, zones are entirely writeable with domains anyway, zones are a better and more sound API for domains but they don't create issues for error handling. There is plenty of discussion in this thread.

Additionally we can probably provide the lower level hooks Angular needs in order to have zones in async/await regardless of zones being a part of ECMAScript.