top | item 8258223

Show HN: Operations.js – Manage async operations in Node and the browser

7 points| mtford | 11 years ago |github.com

4 comments

order

drinchev|11 years ago

I would ask : What is the benefit of operations.js vs promises?

Similar to the examples you can easily do :

    promiseA.then(promiseB).done( ... )

mtford|11 years ago

Yeah, operations.js is meant for more complex scenarios than that. For example if we were spawning hundreds of operations that interact with networks/file systems. We can set an upper limit on concurrent operations using queues and express complex dependencies between them, compose them and cancel them.

LunaSea|11 years ago

I don't see any new features that wouldn't be possible in async. Am I missing something ?

mtford|11 years ago

Hi Luna, from my perspective async.js is about control flow whereas operations.js is about creating well defined operations that can be composed, queued, cancelled, reused and monitored. It's more of a workhorse.