For years I advocated using promises in JS code, now I avoid them if I can. Here's why: https://github.com/mjackson/npm-http-server/pull/17/files#r48298501 …
-
-
Replying to @isntitvacant
@isntitvacant@mjackson hmm I don't think it's so much about zalgo. More like; one promise means promises everywhere :/2 replies 0 retweets 2 likes -
Replying to @mattdesl
@mattdesl@isntitvacant@mjackson foo().then(cb.bind(null, null)).catch(cb)4 replies 0 retweets 1 like -
Replying to @sindresorhus
@sindresorhus@isntitvacant@mjackson also there is the "browser problem"... Polyfills ain't free1 reply 0 retweets 0 likes -
Replying to @mattdesl
@mattdesl@isntitvacant@mjackson The need to polyfill promises will go away eventually. The web is built on polyfills anyways.1 reply 0 retweets 0 likes -
Replying to @sindresorhus
@sindresorhus@mattdesl@mjackson Where possible, I prefer slow-but-correct/safe over fast-but-broken/dangerous.2 replies 0 retweets 1 like
@isntitvacant @sindresorhus @mattdesl @mjackson to me it's about error handling; throw no longer panics
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.
gets somewhat better with system-level onUnhandledRejection.
describes "releasing zalgo" as a positive.