3 ms·

Generators in Python are a very useful feature (lazy sequences, like you said), so maybe I spoke to soon. However, I don't think people should be lauding this f

Generators in Python are a very useful feature (lazy sequences, like you said), so maybe I spoke to soon. However, I don't think people should be lauding this feature as some kind of solution to callback hell. I just feel like priority-wise, users would benefit most from modules (which made it), async/await, maybe class syntactic sugar, then everything else.

masklinn 12y ago
> I don't think people should be lauding this feature as some kind of solution to callback hell. Then async/await is no solution for it either.
- rzimmerman 12y ago
  I think: app.get('/thing', function (req, res) { try { await user = db.get({user: req.user}); res.send({user:user}); } catch { res.send(400); } }); beats the hell out of: app.get('/thing', function (req, res) { db.get({user: req.user}, function (err, user) { if (err) return res.send(400); res.send({user:user}); }); }); especially when you have conditionals or loops that can look like: if (user.name == 'abc') { resp = 5; } else { await resp = db.get_resp({user:user}); } await db.save(something); I suppose it doesn't get rid of callbacks, just makes them readable.
  - nawitus 12y ago
    And the promise version for comparison: app.get('/thing', function (req, res) { db.get({user: req.user}).done(user => { res.send({user:user}); }, error => { res.send(400); }); });
  - masklinn 12y ago
    > I suppose it doesn't get rid of callbacks, just makes them readable. You are the one who stated generators were no solution to callback hell but async/await was, yet here's what your code looks like with generators: app.get('/thing', function* (req, res) { try { let user = yield* db.get({user: req.user}); res.send({user: user}); } catch { res.send(400); } }); ...
RobertKerans 12y ago
FWIW, most of the stuff I've read on using generators to wrangle async has stressed that that's not the aim of the protocol, it's just a useful side-effect. But I think you are right, which is a bit of a shame really, given how useful generators can be - most every detailed article quickly skips through pretend toy examples, then <drumroll>aaaand async

masklinn 12y ago

> I don't think people should be lauding this feature as some kind of solution to callback hell. Then async/await is no solution for it either.

rzimmerman 12y ago
I think: app.get('/thing', function (req, res) { try { await user = db.get({user: req.user}); res.send({user:user}); } catch { res.send(400); } }); beats the hell out of: app.get('/thing', function (req, res) { db.get({user: req.user}, function (err, user) { if (err) return res.send(400); res.send({user:user}); }); }); especially when you have conditionals or loops that can look like: if (user.name == 'abc') { resp = 5; } else { await resp = db.get_resp({user:user}); } await db.save(something); I suppose it doesn't get rid of callbacks, just makes them readable.
- nawitus 12y ago
  And the promise version for comparison: app.get('/thing', function (req, res) { db.get({user: req.user}).done(user => { res.send({user:user}); }, error => { res.send(400); }); });
- masklinn 12y ago
  > I suppose it doesn't get rid of callbacks, just makes them readable. You are the one who stated generators were no solution to callback hell but async/await was, yet here's what your code looks like with generators: app.get('/thing', function* (req, res) { try { let user = yield* db.get({user: req.user}); res.send({user: user}); } catch { res.send(400); } }); ...

RobertKerans 12y ago

FWIW, most of the stuff I've read on using generators to wrangle async has stressed that that's not the aim of the protocol, it's just a useful side-effect. But I think you are right, which is a bit of a shame really, given how useful generators can be - most every detailed article quickly skips through pretend toy examples, then <drumroll>aaaand async