I don&#x27;t really buy the con of async&#x2F;await allowing you to write really long functions. You can do the same thing in completely synchronous logic. Additionally, I don&#x27;t really buy the chopping up of a cohesive process into itty bitty functions. Certainly small, simple function are nice, but when small for smallness sake, you basically end up with unreadable spaghetti code.<p>A benefit the author didn&#x27;t quite touch on is what a boon async&#x2F;await is for branching processes. I&#x27;ve got a block of logic that takes credit card info for Stripe, and it needs to validate user info, tokenize payment info, add it to the user model, and then add the tokenized card to the Stripe customer associated with the card. There are a lot of places this can go wrong or data can fail a validation. In promises, branching mid-flow is a huge pain.<p>The much more interesting issue with callback-driven approach to async, no matter what the sugar, was raised by <a href="http:&#x2F;&#x2F;journal.stuffwithstuff.com&#x2F;2015&#x2F;02&#x2F;01&#x2F;what-color-is-your-function&#x2F;" rel="nofollow">http:&#x2F;&#x2F;journal.stuffwithstuff.com&#x2F;2015&#x2F;02&#x2F;01&#x2F;what-color-is-y...</a>.