Promises don't work well for library internals; they're external API only. Async* style methods cannot be replaced, so what's the point?
-
-
Replying to @yoshuawuyts
I'd much rather have Streams alternatives compete rather than these Promise things; they solve different problems
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
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
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Languages like Go and Rust have syntax to panic and stop execution - in JS this is `throw `- it's mental to destroy those semantics
1 reply 0 retweets 2 likes -
Replying to @yoshuawuyts
I disagree with the premise that developer errors should be handled - at best they should be logged -> process.on('uncaughtexception')
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
nothing is worse than being unable to trace errors - not only do promises break panic, they also inject timers which mess up profiling
1 reply 0 retweets 3 likes
If sugar is poured over a minimal API, then the API is no longer minimal. "Minimum" means least possibly feasible
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.