3 ms·
This is exactly what I was about to write. Also, the amount of "callbacks, that's how it's supposed to be" and "hardware is like that" and "programming is hard,
by nurettin 10y ago
This is exactly what I was about to write. Also, the amount of "callbacks, that's how it's supposed to be" and "hardware is like that" and "programming is hard, deal with it" kind of replies for a readily solved problem are staggering.
- lootsauce 10y agoI don't know about others but the imposition of try catch for error handling in async/await seems to cut against the syntax gains over promises.
- nurettin 10y agoIf by promises you mean the `some.fun(had).catch(had, function(){handle stuff here})` syntax compared to async/await, that is actually a very fair point and it does make two syntaxes similarly verbose. However, it is still easier to follow a ladder of conditional statements using async/await compared to escher-style stairs of callbacks inside callbacks.
- edwinjm 10y agoInteresting. In which language is this "readily solved"?