2 ms·
Exactly - for the longest time, the success / error callback signature was the primary and expected way to handle async code in Node modules, and there was a lo
by Cthulhu_ 8y ago
Exactly - for the longest time, the success / error callback signature was the primary and expected way to handle async code in Node modules, and there was a lot of objection to using promises - in part because at the time it was not stable, and in part because its performance was less compared to callback style.
You don't want to put performance bottlenecks in core and/or frequently used libraries just so it fits your preferred async style. If you REALLY want to pay that price, it's trivial to promisify a library like this - and it doesn't add complexity or size or (worst case) dependencies (like 3rd party promise libraries, as was the case for a long time) to your small, focused library.
- deleted 8y ago[deleted]
- jrochkind1 8y agoi guess these are the downsides of a platform without much stdlib. consensus stdlib doesn't really work, and then things don't work together.