> That was the day I decided JS...

Why? surely having 47 promises and some on the same line is the authors fault?

Promise.prototype.then()'s callback function does not need to be written inline. At some point the author should have realised it hass become difficult to grok quickly and refactored them out using appropriate function names.

If you're doing I/O in an event loop it's either 47 promises or 47 callbacks.

> About two years ago I opened up a smallish JS file (~100 lines ) and it contained 47 promises, some on the same line.

This is exactly what async await is trying to simplify :)

Is there an actual reference for this? Sounds like it was minified or just bad coding style. Which can happen in any language.

Here's hoping it gets even better in future so they can win us both back ;)

---

Great article OP. Thank you very much. I remember using Bluebird and sharing the sentiments of the comment which I am replying to.

You're welcome! It's funny because I actually wanted to practice some inkscape and some infographic making abilities.

Still a long way to go but I'm happy that the content is also appreciated!