3 ms·

This is really true. I feel somehow the problem came when the functional programming gang hijacked it and forced ES6 on us. Promises were so counter intuitive t

This is really true. I feel somehow the problem came when the functional programming gang hijacked it and forced ES6 on us. Promises were so counter intuitive they had to create shortly after async / wait... Don't get me wrong there are alot of great things in ES6, but it was not quite the same language after...

efdee 3y ago
What would you prefer instead of promises? Callbacks?
salwadordali 3y ago
How would you solve the async/await issue then? I think JS handles asynchronicity very elegantly. You just need to create a proper mental model around it. I don't want to go back to the old times of callback hell, that's for sure.
manigandham 3y ago
async/await and promises are both just syntax on top of yield/generators. Most programming languages are just different syntax on top of the same core primitives.
merrywhether 3y ago
> functional programming gang This is a bit of weird assignment, given that the Class syntactic sugar over Prototype was one of the marquee features of that release.