TechEcho

Node 7 is out with async/await behind the flag.

<p><pre><code> // the stream has now been fully read, async in the background </code></pre> What if the file is gigabytes in size?

It's a nice trick but it's unsafe in general. JavaScript libraries usually assume single-threaded event handling. If you start up another event loop from a callback (while some other library's code is already on the stack), you'll probably break it.

Well I hope NodeJS ultimately settles on such a syntax to preempt and resume automatically. I love Golang in this regard since it abstracts out everything using channels, and go-routines (not to compare multiple thread support).

Love the simplicity. Wish it was powered by RxJS <a href="https://github.com/Reactive-Extensions/RxJS" rel="nofollow">https://github.com/Reactive-Extensions/RxJS</a>

Looked at the deasync that this is based on, and it looks like they are trying to reinvent threads? Seems ironic to me.

Node 7 is out with async/await behind the flag.

<p><pre><code> // the stream has now been fully read, async in the background </code></pre> What if the file is gigabytes in size?

Love the simplicity. Wish it was powered by RxJS <a href="https://github.com/Reactive-Extensions/RxJS" rel="nofollow">https://github.com/Reactive-Extensions/RxJS</a>

Looked at the deasync that this is based on, and it looks like they are trying to reinvent threads? Seems ironic to me.

Show HN: Async/await alternative

6 comments

Show HN: Async/await alternative

6 comments