Async approach (developer experience)

[yuchi]

There’s a lot of movement about this.

• What about the co approach? nodejs/NG#1 about ES7 async/await-oriented APIs
• Feature Request: Every async function returns Promise nodejs/node#11 using Promises for async APIs
• 3.0 cancellation overhaul petkaantonov/bluebird#415 about Promises not being a good shape for IO
• Aborting a fetch whatwg/fetch#27 about fecth() not being easily cancellable

[omorandi]

An async API à la node is surely desirable, especially for i/o intensive operations, though I'd be happy to see it callback-based. Promises can be used on top of that

[yuchi]

For sure we have to embrace the async. IMHO the APIs should be async-first.

[petkaantonov]

petkaantonov/bluebird#415 about Promises not being a good shape for IO

That issue is not about promises not being in good shape for I/O at all, there is literally nothing in that issue about that!

[yuchi]

Sorry looks like I eventually copypasted something wrong.

[petkaantonov]

It probably originated from this tweet https://twitter.com/mattpodwysocki/status/583332498844696576 the issue is linked with same reasoning there as well. I tried to ask him why he would link it and got no answer.

[yuchi]

@petkaantonov You’re totally right, and it got caught in my short list of references.

[yuchi]

Closing for obsolescence