standard callback patterns are not intrinsically simpler than promises and more error prone (ever seen a cb run twice? I have)
-
-
Replying to @wycats
but at this point, its too late to change direction. we already have CB apis and they are to stay. having 2 conventions=flustercluck
1 reply 0 retweets 0 likes -
Replying to @altmind
there is no one reliable convention. The callback convention is implemented wrong (cb called multiple times, wrong order) often
1 reply 0 retweets 0 likes -
and XHR isn't even close to a standard callback pattern (nor IDB)
1 reply 0 retweets 1 like -
btw there are way more than just fetch using promises: animation, quota management, web midi, streams, font load, etc etc etc
2 replies 0 retweets 0 likes -
Replying to @wycats
quota window.webkitStorageInfo.requestQuota(type, sz, function cb() {}, function cb() {});
1 reply 0 retweets 0 likes -
Replying to @altmind
callback APIs exist but not standard. Can't promisify (or use async lib) with that. Can use Promise.all with the promise version.
1 reply 0 retweets 0 likes -
Replying to @wycats
i dont doubt it CAN be expressed by promise in new std. but why having 2 conventions is better that having 1 subpar convention?
1 reply 0 retweets 0 likes -
Replying to @altmind
having a legacy API and a new reliable API is much, much better than sticking with a subpar API.
1 reply 0 retweets 2 likes -
Replying to @wycats
btw, do you track angular2 progress? they are claming reactive streams better than promises (cancellable, multiple responses).true?
2 replies 0 retweets 0 likes
I disagree (rather strongly) for single values. I predict they'll change their mind.
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.