@yoshuawuyts why?
-
-
Replying to @jaffathecake
@jaffathecake because they force me to work around them. Functions can be converted to promises, implicit catch is hard to revert.1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts why do you need to work around them?1 reply 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake implicit catch. Exceptions should bubble up3 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts bubble up to what? Should the page crash?1 reply 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake The issue I'm having is that I don't think document.fetch should decide for me if it should or shouldn't.2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts promise rejections hit the console and soon window events https://code.google.com/p/chromium/issues/detail?id=495801 … - what's missing?3 replies 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake if a promise just so happens to wrap an assertion that throws, it will incorrectly catch it. It's bad.1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts you say incorrect/bad, but I'm not sure it is, especially with async functions https://jakearchibald.com/2014/es7-async-functions/ …2 replies 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake yeah, nah. That article does its best to make async look good. Not buying that narrative3 replies 0 retweets 0 likes
@jaffathecake promises are implemented on top of functions, async on top of promises. Browser APIs should have the lowest common denominator
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.