@jaffathecake @yoshuawuyts Actually on second look, i don't find either promise versions readable. Hard to tell the intent with a skim.
-
-
Replying to @KoryNunn
@KoryNunn@yoshuawuyts which part of https://jakearchibald.com/2014/es7-async-functions/#this-time-with-es7-async-functions … do you get lost at?2 replies 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake@yoshuawuyts Didn't get lost, just not quick to understand intent. By quick I mean a few seconds. Named tasks help IMO.1 reply 0 retweets 0 likes -
Replying to @KoryNunn
@KoryNunn@yoshuawuyts is that what the first args are in that chaining thing in your example? It's so contrived it doesn't look like JS.1 reply 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake@yoshuawuyts lol thanks for the feedback.. signature: ('taskResultName', ['dependant', 'task', 'names'], task)1 reply 0 retweets 0 likes -
Replying to @KoryNunn
@KoryNunn@yoshuawuyts that seems a lot more complicated than await thingThatReturnsPromise();2 replies 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake@KoryNunn I'm still not seeing why web APIs would have such strong opinions against just passing functions around. Why catch?2 replies 1 retweet 1 like -
Replying to @yoshuawuyts
@yoshuawuyts@KoryNunn the goal here is async functions. Callbacks do not get us there.2 replies 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake@KoryNunn that is an untrue. All you are doing is assuring they won't by banning them from newer APIs. Please reconsider1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts@KoryNunn you have a visceral dislike of promises & async funcs. This is not universally shared. I guess just… get over it.2 replies 0 retweets 0 likes
@jaffathecake I thought the point of the web was to be a target platform not a place to bolster opinions on how people should structure code
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.