yosh

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 

@a0viedo eh, I don't run into problems with that

@a0viedo I only ever use https://github.com/npm/dezalgo  for async guarantees, but those just make timers consistent for every resolution of a call