seems hard to imagine *real-world* async workloads without IO. Trying to imagine how that could arise.
-
-
async parsers might be a good test case!
1 reply 0 retweets 0 likes -
Replying to @isntitvacant @wycats and
I have a good one. Imagine your IO has a caching layer, and a properly primed cache mitigates the IO
1 reply 0 retweets 0 likes -
Replying to @stefanpenner @isntitvacant and
One awesome feature of promises/async is the system should work regardless of if the data is foreign
1 reply 0 retweets 0 likes -
Replying to @stefanpenner @wycats
although not using async/await today yet, ember-data would be such an example.
@isntitvacant@bmeurer@cpojer1 reply 0 retweets 0 likes -
Replying to @stefanpenner @isntitvacant and
ah yes. Skylight's backend works like this, but not written in JS.
1 reply 0 retweets 1 like -
Replying to @wycats @stefanpenner and
TLDR "maybe but not usually async". Good call.
1 reply 0 retweets 0 likes -
-
Replying to @stefanpenner @wycats and
I’ve seen lots of sad/buggy code resulting from: if foreign do X, if local do Y…
1 reply 0 retweets 0 likes -
Replying to @stefanpenner @wycats and
if asyncawait/promise can approach zero cost” we will see simpler less edge casey performant code
2 replies 0 retweets 0 likes
totally agree. Was psyched by Mozilla on this this week.
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.