dfilatov/vow

browsers polyfill

JiLiZART opened this issue · 8 comments

JiLiZART commented

Any plans to polyfill or use build-in Promise ?

dfilatov commented

What for? Is there any valuable reason (excluding "wow, native promise") to do that?
What's more, it's not possible to implement some of features via native promise, for instance, synchronously get a value of already resolved promise.

JiLiZART commented

Currently i use vow with bem-core, plus some libs, thats use Promise, but
IE don't have any support for it. Its would be useful if i can use only one
Promise lib in whole project, rather than use polyfill, doing the same job
as vow.
Ср, 25 мая 2016 в 11:02, Filatov Dmitry notifications@github.com:

What for? Is there any valuable reason (exluding "wow, native promise") to
do that?
What's more, it's not possible to implement some of features via native
promise, for instance, synchronously get a value of already resolved
promise.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#102 (comment)

dfilatov commented

As I wrote before, unfortunately, there's no way to implement all of vow api on top of native promises api.

Guria commented

@dfilatov I think @JiLiZART do not ask to implement vow api on top of native promises, but instead use vow as polyfill. So if current environment doesn't have native Promise it could be polyfilled with vow.

Guria commented

@JiLiZART have you tried smth like window.Promise = window.Promise || vow.Promise ?

JiLiZART commented

@Guria no, i'll try

dfilatov commented

Vow should properly work as a polyfill for native promises. Let me know if it doesn't.