About two years ago I opened up a smallish JS file (~100 lines ) and it contained 47 promises, some on the same line.
That was the day I decided JS had gotten way too far up it's own ass and abandoned my career in web development. Every day that goes by makes it seem like a better and better decision.
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.
Thank you for the date references. I just finished reading a book on Node/SailsJS and this is a great summary and overview. I’m an app developer by day but spend a lot of time keeping current on other technologies.
13 comments
[ 2.6 ms ] story [ 35.1 ms ] threadThat was the day I decided JS had gotten way too far up it's own ass and abandoned my career in web development. Every day that goes by makes it seem like a better and better decision.
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.
This is exactly what async await is trying to simplify :)
---
Great article OP. Thank you very much. I remember using Bluebird and sharing the sentiments of the comment which I am replying to.
Still a long way to go but I'm happy that the content is also appreciated!