News for hackers. Stuff that matters.
Re:Skills Poor Programmers Lack by r4mbini on Sunday July 21, 2019 @02:21PM (#20492805)
> In JavaScript, this is often indicated by new Promise inside a .then().

I have found myself doing this sometimes, why is it considered bad practice?

Re:Skills Poor Programmers Lack by kevsim on Sunday July 21, 2019 @02:29PM (#20492851)
I guess because inside of a then() you can simply return the success case and throw the error case, no need to create a new Promise and call the resolve/reject functions.
Re:Skills Poor Programmers Lack by rounce on Sunday July 21, 2019 @02:55PM (#20493009)
Was trying to think of exceptions to this when I read and and could only think of one: When you need to wrap a callback API with unusual callback arguments, where a `promisify` like helper won't work. Then again, I still feel the wrapping function should be defined outside of the `then`, as it feels like this is a separate utility to the work being done in the Promise chain.
Re:Skills Poor Programmers Lack by r4mbini on Sunday July 21, 2019 @03:05PM (#20493062)
This is the context I’ve used it in
Re:Skills Poor Programmers Lack by r4mbini on Sunday July 21, 2019 @02:44PM (#20492942)
Ah ok, they’re saying don’t use a new promise to do async logic not don’t use them for more sync things later down the chain. Thank you!