← Back to Topics

JavaScript Promises

This cluster centers on debates about using Promises for asynchronous programming in JavaScript, including their limitations, comparisons to async/await, generators, and alternative libraries.

📉 Falling 0.3x Programming Languages
3,478
Comments
18
Years Active
5
Top Authors
#7868
Topic ID

Activity Over Time

2009
9
2010
11
2011
34
2012
77
2013
261
2014
253
2015
341
2016
394
2017
376
2018
256
2019
229
2020
240
2021
167
2022
238
2023
228
2024
202
2025
157
2026
5

Top Contributors

spion (55) inglor (50) WorldMaker (29) tlrobinson (19) franciscop (18)

Keywords

babeljs.io response.json Promises.all JavaScript ES6 github.com ES2015 API adstruc.com promises promise async await bytes async await const resolve generators es6

Sample Comments

whatwherewhy • Nov 7, 2022 • View on HN

What's the reasoning for using this over promise and/or async?

_v7gu • Jun 19, 2017 • View on HN

Promises returning promises (or async/await which is just sugar-coating for promises) solves this very cleanly in my experience

mikewhy • Apr 7, 2017 • View on HN

Promises are the backbone of async/await.

chx • Jun 19, 2017 • View on HN

Didn't ES6 promise ;) to solve this?

fwip • Feb 15, 2018 • View on HN

It sounds like the author wants coroutines, not promises.

epicide • Aug 9, 2017 • View on HN

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

andrus • Apr 30, 2014 • View on HN

The Promises/A+ assumption that you'd never want a Promise to return a Promise is really shortsighted.

voidr • Dec 10, 2013 • View on HN

Why not just use the Promise API?

Nemcue • May 10, 2015 • View on HN

Why not use a Promise library instead?

embwbam • Jul 27, 2013 • View on HN

Promises are the only real solution. https://github.com/kriskowal/q