My concerns for async/await grow even greater https://esdiscuss.org/topic/async-await-improvements#content-40 …
-
-
Replying to @jlongster
@jlongster browsers REALLY need to get their shit together and make their error tooling understand promises2 replies 3 retweets 2 likes -
Replying to @wycats
@wycats@jlongster yes they need to get there shit together.2 replies 0 retweets 1 like -
Replying to @stefanpenner
@stefanpenner@wycats yeah. 1. unfortunately current semantics does make it quite difficult...3 replies 0 retweets 0 likes -
Replying to @jlongster
@jlongster@stefanpenner people think they want "top level" async funcs to throw, but that means white screen in prod. White screen no-no2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@stefanpenner I dunno, if a top-level error happens your app is probably borked no matter what4 replies 0 retweets 0 likes -
Replying to @jlongster
@jlongster@stefanpenner in other words, "top level" is relative. You might be done with a promise but passing it to something that cares.3 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@stefanpenner sure, that is cool but I believe there are other ways to do that (that are more verbose though, and explicit)1 reply 0 retweets 0 likes -
Replying to @jlongster
@jlongster@stefanpenner Easy to believe lots of things. Creating extra kinds of functions for debugging is a no-no for me.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@stefanpenner Anything abstract like this is easy throw around, yes. I think to think we each develop robust, mature software tho.1 reply 0 retweets 0 likes
@jlongster @stefanpenner absolutely. Explicitness works well for the most advanced. Too explicit and it gets hard to explain and use.
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.