Is it just me, or does their example of the traditional way of doing those calls user literally the least efficient possible way of writing that code?
Surely using async/await would get you to something nearly as clean as their end-state
Surely using async/await would get you to something nearly as clean as their end-state
It sounds like FibJS supports async/await as well, but that just means there are two ways of doing things: I suspect a big reason promises won out is because they could be easily polyfilled into browsers, and a bit part of NodeJS’s appeal was using the same libraries on both sides.
If you've ever tried to build it, you'd understand why there's suddenly multiple options.