yosh

Promises don't work well for library internals; they're external API only. Async* style methods cannot be replaced, so what's the point?

I'd much rather have Streams alternatives compete rather than these Promise things; they solve different problems

Again: if the point is to parse data over time, then we should think about how to improve streams - Promises are geared to be one-off

Languages like Go and Rust have syntax to panic and stop execution - in JS this is `throw `- it's mental to destroy those semantics

I disagree with the premise that developer errors should be handled - at best they should be logged -> process.on('uncaughtexception')

@yoshuawuyts what do you mean by "developer errors"?

@a0viedo I use assert to validate function arg types; type mismatch should never happen; swallowing those is harmful

@yoshuawuyts even after type checking, you have to ensure the callback parameter is only called once, e.g https://www.npmjs.com/package/once