I really don't understand how anyone is actually using Promises for fetching web content. The model seems -so- broken.
-
-
Replying to @toshok
I mean, I understand the code - I just wonder how people who write it can sleep at night. I can't.
3 replies 0 retweets 1 like -
Replying to @toshok
JS needs something closer to .net Task<T>. Something supporting cancellation. Use that to implement async/await, not Promises.
1 reply 0 retweets 4 likes -
Replying to @BrendanEich @wycats
I'd heard about cancelable Promises. I just fear we'll get async/await before we get them. Reasonable worry?
1 reply 0 retweets 0 likes -
additional worry: cancellation goes in in a way that can't be used for async/await.
1 reply 0 retweets 0 likes -
That would be a big failure on TC39's part, wouldn't it?
1 reply 0 retweets 0 likes -
Replying to @BrendanEich @wycats
depends. features could be viewed as orthogonal
1 reply 0 retweets 0 likes -
Nope. Language designers must make features compose. see Scheme report intro: http://www.schemers.org/Documents/Standards/R5RS/HTML/r5rs-Z-H-3.html#%_chap_Temp_3 … first paragraph.
1 reply 0 retweets 0 likes -
Replying to @BrendanEich @wycats
no argument there. more arguing schedule constraints, lack of champions could lead to ordering that doesn't compose.
3 replies 0 retweets 0 likes
the point of TC39, as it currently stands, is to make sure champions hear cross-cutting concerns before advancing.
-
-
one of the points - important!
0 replies 0 retweets 3 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.