Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I've been using Node 8 again after a few years of staunchly avoiding it, and the pain of selecting the right kind of libraries to use async/await sanely without having to massage promises (and .then()) is still there - in that sense, I feel very much like that cat with the strawberry beret on the article heading...


Why are you having to bring in libraries to use async/await? What does the native implementation not provide?


I'm not bringing in libraries. I'm trying to put together a set of libraries that work well with async for my purposes (custom net I/O, databases, etc.) without having to wrap them or fiddle with resolving promises on my own.


Is there something in particular that you do not like about Promises?


Yeah, having to deal with inconsistency across libraries inside the same project.


I don't really see how Promises leads to that... do you mean the fact that not all libraries support them out of the box?

Bluebird (probably my favorite Promises implementation) has nice features to interface pretty easily between callbacks and Promises.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: