Finish this sentence: I would use native promises (instead of bluebird, RSVP) if only they _________.
-
-
but at this point, its too late to change direction. we already have CB apis and they are to stay. having 2 conventions=flustercluck
-
there is no one reliable convention. The callback convention is implemented wrong (cb called multiple times, wrong order) often
-
and XHR isn't even close to a standard callback pattern (nor IDB)
-
btw there are way more than just fetch using promises: animation, quota management, web midi, streams, font load, etc etc etc
-
quota window.webkitStorageInfo.requestQuota(type, sz, function cb() {}, function cb() {});
-
callback APIs exist but not standard. Can't promisify (or use async lib) with that. Can use Promise.all with the promise version.
-
i dont doubt it CAN be expressed by promise in new std. but why having 2 conventions is better that having 1 subpar convention?
-
having a legacy API and a new reliable API is much, much better than sticking with a subpar API.
- 2 more replies
New conversation -
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.