Hacker News Reader

Maybe I'm missing something, but I find C#'s async/await much more intuitive (not having written any C# and currently working on a pet project using promises with Node and Q).

My issue with promises is that I find myself working around the API/language when I actually want synchronous code. My app calls a JSON API and then writes the results to three tables (in sequence). In "normal", blocking code:

  results = getResults(); writeTable1(results.foo); writeTable2(results.bar); writeTable3(results.baz);

Using Node and Q:

  db.load().then(()-> setupDB(db)).then(()-> collectData(db)).done()

In which setupDB() returns a chain of three promises and collectData, which loops through the results and attach a new promise to the chain in order to return a chain of `n` promises.

Are these just growing pains of learning a new paradigm or am I using the wrong tool for the job?

Can someone point me to any projects that actually use promises?

View on HN

// Sync var foo = function () { return 'foo' }; var addBar = function (foo) { return foo + 'bar'; } addBar(foo()) == 'foobar' // Promise using Q var foo = function () { return Q.resolve('foo') }; var addBar = function (foo) { return Q.resolve(foo + 'bar'); } foo.then(addBar).done(function (result) { result == 'foobar' });